yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #84914
[Bug 1903545] Re: Nova does not support older than N - 1 computes but does not prevent such error situation either
Victoria backport has been merged: https://review.opendev.org/c/openstack/nova/+/761924
Ussuri backport has been proposed: https://review.opendev.org/c/openstack/nova/+/770764
** Changed in: nova/victoria
Status: In Progress => Fix Released
** Changed in: nova/victoria
Status: Fix Released => Fix Committed
** Changed in: nova/victoria
Importance: Undecided => Low
** Changed in: nova/ussuri
Status: New => In Progress
** Changed in: nova/ussuri
Importance: Undecided => Low
** Changed in: nova/ussuri
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
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/1903545
Title:
Nova does not support older than N - 1 computes but does not prevent
such error situation either
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) train series:
New
Status in OpenStack Compute (nova) ussuri series:
In Progress
Status in OpenStack Compute (nova) victoria series:
Fix Committed
Bug description:
This bug report is theoretic right now as I don't have actual data for
a failure scenario. Please add details below if you have one.
Nova supports rolling upgrade of nova-compute services by keeping the
compute RPC interface compatible between N and N - 1 (where N is a
nova major release, like Wallaby). Still nova does not prevent to have
a deployment with older than N - 1 computes. Some operations will
still work but some will fail with hard to debug errors, or even leave
your deployment in an inconsistent state.
Nova should prevent such inconsistencies.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1903545/+subscriptions
References