openstack
/
nova
Code Issues Proposed changes

Merge "Change nova-next job to run with python3"

This commit is contained in:
Zuul 2019-02-13 18:52:58 +00:00 committed by Gerrit Code Review
parent 104d79d8dd ab72dd4096
commit 7e3ad4eec6
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.zuul.yaml
View File

@ -162,6 +162,7 @@
post-test scripts to ensure those scripts are still working,
e.g. archive_deleted_rows. In Queens, this job started testing the
TLS console proxy code in the libvirt driver.
Starting in Stein, the job was changed to run with python 3.
run: playbooks/legacy/nova-next/run.yaml
post-run: playbooks/legacy/nova-next/post.yaml

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

@ -24,9 +24,6 @@
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
# TODO(mriedem): Consider setting USE_PYTHON3=True here to make this
# job run under python 3.5 which is a "next" type thing.
# Enable TLS between the noVNC proxy & compute nodes; this requires
# the tls-proxy service to be enabled.
@ -43,6 +40,7 @@
NOVA_USE_SERVICE_TOKEN=True
NOVA_CONSOLE_PROXY_COMPUTE_TLS=True
PLACEMENT_DB_ENABLED=True
USE_PYTHON3=True
[[post-config|$NOVA_CONF]]
[compute]