yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

At every FFU session we talk about the "nova-status upgrade check" CLI
but it's surprisingly missing from the nova upgrade docs:

https://docs.openstack.org/nova/latest/user/upgrade.html

I'm not exactly sure where in the docs we should mention it, probably
early in the process, or as one of the steps, but we should mention that
you should run that (it can be run before and after a base install or an
upgrade):

https://docs.openstack.org/nova/latest/cli/nova-status.html

Note that the "verify operation" post-install step mentions running the
CLI:

https://docs.openstack.org/nova/latest/install/verify.html

So maybe we can work that into the pre and post upgrade checks in the
upgrade docs.

Questions to answer:

* when do you run it? before or after you upgrade?
* which version do you run? if i'm upgrading from pike to queens, do i run the nova-status code from pike or queens?

** Affects: nova
     Importance: Medium
         Status: Confirmed


** Tags: docs upgrade

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

Title:
  The nova upgrade docs don't mention the nova-status upgrade check CLI

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  At every FFU session we talk about the "nova-status upgrade check" CLI
  but it's surprisingly missing from the nova upgrade docs:

  https://docs.openstack.org/nova/latest/user/upgrade.html

  I'm not exactly sure where in the docs we should mention it, probably
  early in the process, or as one of the steps, but we should mention
  that you should run that (it can be run before and after a base
  install or an upgrade):

  https://docs.openstack.org/nova/latest/cli/nova-status.html

  Note that the "verify operation" post-install step mentions running
  the CLI:

  https://docs.openstack.org/nova/latest/install/verify.html

  So maybe we can work that into the pre and post upgrade checks in the
  upgrade docs.

  Questions to answer:

  * when do you run it? before or after you upgrade?
  * which version do you run? if i'm upgrading from pike to queens, do i run the nova-status code from pike or queens?

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