Nova does not support older than N - 1 computes but does not prevent such error situation either

Bug #1903545 reported by Balazs Gibizer on 2020-11-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Balazs Gibizer
Train
Undecided
Unassigned
Ussuri
Low
Balazs Gibizer
Victoria
Low
Balazs Gibizer

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.

Balazs Gibizer (balazs-gibizer) wrote :
Changed in nova:
assignee: nobody → Balazs Gibizer (balazs-gibizer)
tags: added: upgrade
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
status: Confirmed → Fix Released
Balazs Gibizer (balazs-gibizer) wrote :

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

This issue was fixed in the openstack/nova 22.1.0 release.

This issue was fixed in the openstack/nova 21.2.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers