ghanshyam d74a5b23a5 Disable the tls-proxy in nova-next & fix nova-tox-functional-py35 parent ... While moving the legacy job nova-next on bionic, tls-proxy did not work and leads to nova-next job fail. To proceed further on Bionic migration which is blocked by nova-next failure, this commit temporary disable the tls-proxy service until bug#1819794 is fixed. Also this updates the parent of nova-tox-functional-py35 from openstack-tox to openstack-tox-functional-py35 in order to handle the upcoming change of the infra CI default node type from ubuntu-xenial to ubuntu-bionic. The python3.5 binary is not provided on ubuntu-bionic and the shared "py35" job definitions in the openstack-zuul-jobs repository have been patched to force them to run on ubuntu-xenial [1]. We should inherit from one of these jobs for jobs that rely on python3.5. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003746.html Related-Bug: #1819794 Change-Id: Ie46311fa9195b8f359bfc3f61514fc7f70d78084		2019-03-13 23:46:19 +00:00
..
nova-cells-v1	Make nova-cells-v1 run with neutron	2018-03-15 09:25:00 -04:00
nova-grenade-live-migration	Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree	2019-02-28 21:40:30 -05:00
nova-live-migration	Test live migration with config drive	2019-02-28 10:54:01 -05:00
nova-lvm	Address comments from I51adbbdf13711e463b4d25c2ffd4a3123cd65675	2018-02-06 16:53:36 -05:00
nova-next	Disable the tls-proxy in nova-next & fix nova-tox-functional-py35 parent	2019-03-13 23:46:19 +00:00