Nova Console setup broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
melanie witt |
Bug Description
Devstack patch [1] broke the nova console configuration. It moves the console config (vnc, spice, serial) from the nova.conf file into nova cells file when $CELLSV2_SETUP != "singleconductor". Due to that the console is not applied in nova-compute .
This causes the s390x zkvm third party CI to fail.
* nova configuration [2]
* Devstack command to start n-cpu: local 'command=
I'm not a cell expert, but from my point of view there are 2 solutions
* always configure console in n-cpu
* start n-cpu with the nova cells config file...
Patch [4] from Stephen will not fix the issue, as the method "configure_
[1] https:/
[2] http://
[3] http://
[4] https:/
[5] https:/
description: | updated |
description: | updated |
description: | updated |
description: | updated |
In nova, we recently migrated from the nova-consoleauth service backend to the database backend for console token authorization storage and thus the layout for running console proxies changed from global => per cell. So the console proxies need to consume the cell config to obtain vnc/spice/serial settings instead of the global nova.conf.
Patch [1] aimed to move vnc/spice/serial settings from global nova.conf => cell nova.conf for that reason *BUT* it looks like what I missed is that the nova-cpu.conf begins its life as a copy of the global nova.conf:
https:/ /github. com/openstack- dev/devstack/ blob/master/ lib/nova# L905
so that's why vnc/spice/serial settings disappeared from nova-cpu.conf unintended.
I'll come up with a fix for that.