vnc console fail when changing NovaLibvirtNetwork to e.g. ctlplane
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Martin Schuppert |
Bug Description
Deployment with the following THT param make the vnc console to fail:
parameter_defaults:
ServiceNetMap:
Steps to Reproduce:
1. Deploy with THT parameter:
ServiceNetMap:
2. Run tempest test tempest.
3. Test fails
Actual results:
Body: {"os-getVNCCons
Response - Headers: {'status': '200', u'content-length': '144', 'content-location': 'https:/
Body: {"console": {"url": "https:/
}}}
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
'Token must be invalid because the connection '
File "/usr/lib/
raise self.failureExc
AssertionError: True is not false : Token must be invalid because the connection closed.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → wallaby-3 |
importance: | High → Medium |
tags: | added: queens-backport-potential |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
the issue is that we have NovaVncProxyNetwork [1], NovaLibvirtNetwork [2] and NovaApiNetwork [3] being used for vnc configuration. We should move to use one network for vnc configuration, probably the NovaLibvirtNetwork as this is also used in couple of places, e.g. live migration. If one of the networks get changed from internal_api the service configuration between libvirt, nova-compute and novnc proxy gets inconsistent and the console is broken as seen from the tempest test.
[1] https:/ /github. com/openstack/ tripleo- heat-templates/ blob/master/ deployment/ nova/nova- compute- container- puppet. yaml#L1102 /github. com/openstack/ tripleo- heat-templates/ blob/master/ deployment/ nova/nova- libvirt- container- puppet. yaml#L441 /github. com/openstack/ tripleo- heat-templates/ blob/master/ deployment/ nova/nova- vnc-proxy- container- puppet. yaml#L256
[2] https:/
[3] https:/