yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76318
[Bug 1798188] Re: VNC stops working in rolling upgrade by default
This is considered fixed since https://review.openstack.org/611214
merged, since an update to the rocky release note went directly to the
stable/rocky branch and not to master. The patch used "Partial-Bug" in
the commit message because it was intended to go alongside a release
note patch to close out the bug, but the release note patch was stable-
only and went only to the stable/rocky branch.
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1798188
Title:
VNC stops working in rolling upgrade by default
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) rocky series:
Fix Committed
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1798188/+subscriptions
References