yahoo-eng-team team mailing list archive

[Sylvain Bauza <1956983@xxxxxxxxxxxxxxxxxx>]

I'm not sure I'd classify it as a bug. Probably a good thought so, so
marking it Invalid/Wishlist but I'm open to thoughts.

To answer your question, now that we have an hardstop blocking nova
services to restart if there are old enough, this sound a legit
blueprint to address.

** Changed in: nova
   Importance: Undecided => Wishlist

** Changed in: nova
       Status: New => Invalid

-- 
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/1956983

Title:
  Consider making upgrade check for old computes a failure

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Currently, the upgrade check for older than N-1 computes only produces a warning.
  For example:

  Check: Older than N-1 computes
  Result: Warning
  Details: Current Nova version does not support computes older than
    Victoria but the minimum compute service level in your
    system is 30 and the oldest supported service level is 52.

  If this is overlooked, Nova services will fail to start after upgrade.
  With Nova API down, the old services cannot be removed without
  database edits.

  Is there a specific reason to keep this check as a warning rather than
  a failure?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1956983/+subscriptions