yahoo-eng-team team mailing list archive

[Dmitriy Rabotyagov <2040264@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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://paste.openstack.org/show/biUIcOzMCx0YlsFob2KK/

Nova-conductor does negotiation by minimal version:
INFO nova.compute.rpcapi [None req-2670be51-8233-4269-ac6a-f49486e8893d - - - - - -] Automatically selected compute RPC version 6.1 from minimum service version 64

Potentially, there's another issue upgrading from Yoga to 2023.1 related to this:
https://github.com/openstack/nova/commit/30aab9c234035b49c7e2cdc940f624a63eeffc1b#diff-47eb12598e353b9e0689707d7b477353200d0aa3ed13045ffd3d017ee7d9e753R3709

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  VM rebuild fails after Zed->2023.1 upgrade

Status in OpenStack Compute (nova):
  New

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://paste.openstack.org/show/biUIcOzMCx0YlsFob2KK/

  Nova-conductor does negotiation by minimal version:
  INFO nova.compute.rpcapi [None req-2670be51-8233-4269-ac6a-f49486e8893d - - - - - -] Automatically selected compute RPC version 6.1 from minimum service version 64

  Potentially, there's another issue upgrading from Yoga to 2023.1 related to this:
  https://github.com/openstack/nova/commit/30aab9c234035b49c7e2cdc940f624a63eeffc1b#diff-47eb12598e353b9e0689707d7b477353200d0aa3ed13045ffd3d017ee7d9e753R3709

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