yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

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.

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Changed in: nova/rocky
       Status: New => Confirmed

** Changed in: nova/rocky
   Importance: Undecided => High

-- 
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):
  Confirmed
Status in OpenStack Compute (nova) rocky series:
  Confirmed

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