openstack
/
nova
Code Issues Proposed changes

Re-enable testing of console with TLS in nova-next job 

This is a partial revert of Ie46311fa9195b8f359bfc3f61514fc7f70d78084.

Depends-On: https://review.openstack.org/643045

Related-Bug: #1819794

Change-Id: I1bf37edb4dc3bdb6f23d077eae32e81ef48bdcdc
This commit is contained in:
melanie witt 2019-03-22 01:27:45 +00:00
parent 926e584136
commit 872a9b4e7c
1 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
playbooks/legacy/nova-next/run.yaml
View File

@ -38,10 +38,7 @@
cat << 'EOF' >>"/tmp/dg-local.conf"
[[local|localrc]]
NOVA_USE_SERVICE_TOKEN=True
# TODO (gmann): enable TLS console proxy once
# bug#1819794 is fixed. Something to take care
# while moving these jobs to devstack zuulv3 jobs.
# NOVA_CONSOLE_PROXY_COMPUTE_TLS=True
NOVA_CONSOLE_PROXY_COMPUTE_TLS=True
USE_PYTHON3=True
ENABLE_VOLUME_MULTIATTACH=True
@ -58,11 +55,7 @@
cmd: |
set -e
set -x
# tls-proxy is needed to initialize the CA and cert.
# TODO (gmann): enable TLS console proxy once
# bug#1819794 is fixed. Something to take care
# while moving these jobs to devstack zuulv3 jobs
# export ENABLED_SERVICES=tls-proxy
export ENABLED_SERVICES=tls-proxy
export PYTHONUNBUFFERED=true
# Yes we want to run Tempest.
export DEVSTACK_GATE_TEMPEST=1