openstack
/
grenade
Code Issues Proposed changes

Set NOVA_VNC_ENABLED: true for subnode in the grenade job 

Currently, because we don't run the n-novnc (console proxy) service on
the subnode, devstack won't enable VNC for guests hosted on the
subnode.

We see occasional failures in the gate when VNC tempest tests attempt
to obtain a VNC console for a guest that happened to get scheduled to
the subnode with the following error:

  Details: {'code': 400, 'message': 'Unavailable console type novnc.'}

This sets NOVA_VNC_ENABLED = true for the subnode only, with the
thinking that the enabled n-novnc service is sufficient for the
controller node.

Jobs that derive from the "devstack" job [1] are already setting
NOVA_VNC_ENABLED: true for both the controller node and subnode.

[1] 3ffcc89d5d/.zuul.yaml (L535)

Change-Id: I1acbdb605e0e0d9e5b4604fcd21af850b06823b9
This commit is contained in:
melanie witt 2023-11-06 23:25:26 +00:00
parent 36c8d242f8
commit f1980a682b
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.zuul.yaml
View File

@ -316,6 +316,11 @@
Q_HOST: "{{ hostvars['controller']['nodepool']['private_ipv4'] }}"
RABBIT_HOST: "{{ hostvars['controller']['nodepool']['private_ipv4'] }}"
DATABASE_HOST: "{{ hostvars['controller']['nodepool']['private_ipv4'] }}"
# We need to set this for the subnode to tell devstack to enable
# VNC for guests that are hosted on the subnode. Otherwise,
# devstack won't know to enable it given that we don't enable the
# n-novnc (console proxy) service on the subnode.
NOVA_VNC_ENABLED: true
- job:
name: grenade-py3