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

[Balazs Gibizer]

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)]

Fixed by https://review.opendev.org/#/c/738482/ on master

[Balazs Gibizer (balazs-gibizer)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Elod Illes <email address hidden>" on branch: stable/train
Review: https://review.opendev.org/c/openstack/nova/+/779293
Reason: stable/train branch of nova projects' have been tagged as End of Life. All open patches have to be abandoned in order to be able to delete the branch.

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Elod Illes <email address hidden>" on branch: stable/train
Review: https://review.opendev.org/c/openstack/nova/+/779294
Reason: stable/train branch of nova projects' have been tagged as End of Life. All open patches have to be abandoned in order to be able to delete the branch.