Comment 6 for bug 1819794

Reviewed: https://review.openstack.org/643129
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d74a5b23a59e552159b57a0a42a23ff08215941b
Submitter: Zuul
Branch: master

commit d74a5b23a59e552159b57a0a42a23ff08215941b
Author: ghanshyam <email address hidden>
Date: Wed Mar 13 18:12:41 2019 +0000

    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