VNC stops working in rolling upgrade by default
Bug #1798188 reported by
Mohammed Naser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
melanie witt | ||
Rocky |
Fix Committed
|
High
|
melanie witt |
Bug Description
During a rolling upgrade, once the control plane is upgraded and running on Rocky (but computes still in Queens), the consoles will stop working.
It is not obvious however it seems that the following is missing:
```
[workarounds]
enable_consoleauth = True
```
There isn't a really obvious document or anything explaining this, leaving the user confused
Changed in nova: | |
assignee: | nobody → melanie witt (melwitt) |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: console upgrade |
To post a comment you must log in.
One suggestion in IRC today was that we could add a "nova-status upgrade check" which iterates the cell DBs looking to see if there are any non-deleted/ disabled nova-consoleauth services table records and if so, check to see if there are no console_auth_tokens entries in that DB and if [workarounds] /enable_ consoleauth is False, fail (or warn?) the status check b/c it means that cell is using nova-consoleauth but doesn't have tokens in the DB so it needs to run the consoleauth service.