yahoo-eng-team team mailing list archive

[Mark Goddard <mark@xxxxxxxxxxxx>]

Public bug reported:

Description
===========

When performing an upgrade, services cap their RPC version when
communicating with nova-compute to that of the compute service with the
lowest version. Once all computes are running the new version, we can
restart the services to remove this cap.

When deployment tools try to automate this procedure there is no
interface available to check or wait for all computes to be running the
new version.

Steps to reproduce
==================

Perform a rolling upgrade of nova, following
https://docs.openstack.org/nova/latest/user/upgrade.html.

Expected results
================

After starting up nova services with the new code, there is some way to
check which compute services are running the latest RPC version (from
the 'services' DB table). Ideally it would not be necessary for the
caller to know the actual minimum RPC version.

Actual results
==============

We need to insert a manual step to check the service versions in the
database, or a 'sleep' for long enough that we can be sure that all
services are up and running the new version.

** 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/1833542

Title:
  No mechanism to wait for computes to update service version before
  restarting to remove RPC version cap after upgrade

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========

  When performing an upgrade, services cap their RPC version when
  communicating with nova-compute to that of the compute service with
  the lowest version. Once all computes are running the new version, we
  can restart the services to remove this cap.

  When deployment tools try to automate this procedure there is no
  interface available to check or wait for all computes to be running
  the new version.

  Steps to reproduce
  ==================

  Perform a rolling upgrade of nova, following
  https://docs.openstack.org/nova/latest/user/upgrade.html.

  Expected results
  ================

  After starting up nova services with the new code, there is some way
  to check which compute services are running the latest RPC version
  (from the 'services' DB table). Ideally it would not be necessary for
  the caller to know the actual minimum RPC version.

  Actual results
  ==============

  We need to insert a manual step to check the service versions in the
  database, or a 'sleep' for long enough that we can be sure that all
  services are up and running the new version.

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