VM rebuild fails after Zed->2023.1 upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Committed
|
Undecided
|
Unassigned | ||
2024.1 |
Fix Committed
|
Undecided
|
Unassigned | ||
Antelope |
New
|
Undecided
|
Unassigned | ||
Bobcat |
New
|
Undecided
|
Unassigned | ||
Zed |
New
|
Undecided
|
Unassigned |
Bug Description
Description
===========
After upgrade of nova, including compute and conductor nodes, VM rebuild fails. All computes, that have service state UP, and all conductors are having version 66. Though, there was 1 compute during upgrade that is DOWN, which does have version 64.
Due to it conductor negotiates minimal version to 64, which is still acceptable minimal RPC version though that leads to not passing another required argument.
Steps to reproduce
==================
* Setup env with Nova version 26.2.0
* Perform upgrade to 27.1.0 where 1 compute will be down or not upgraded (and thus can't update it's rpc version to latest 66)
* Try to re-build the VM: openstack server rebuild <server_uuid> --image <image_uuid>
Expected result
===============
VM is rebuild
Actual result
=============
VM is stuck in rebuilding state with following trace in nova-compute
Logs & Configs
==============
Stack trace from nova-compute:
https:/
Nova-conductor does negotiation by minimal version:
INFO nova.compute.rpcapi [None req-2670be51-
Potentially, there's another issue upgrading from Yoga to 2023.1 related to this:
https:/
Changed in nova: | |
status: | New → Fix Committed |
Related fix proposed to branch: master /review. opendev. org/c/openstack /nova/+ /899234
Review: https:/