Hongbin Lu 7cc9500f5a Trivial fixes in upgrade check docs

This addresses the outstanding comments in
https://review.openstack.org/#/c/611418/

Change-Id: I77c977b6b9af0c31304ae6848fcde2b522c0c4d8

2018-10-21 19:19:38 +00:00

1.9 KiB

Raw Blame History

zun-status

CLI interface for Zun status commands

Synopsis

zun-status <category> <command> [<args>]

Description

zun-status is a tool that provides routines for checking the status of a Zun deployment.

Options

The standard pattern for executing a zun-status command is:

zun-status <category> <command> [<args>]

Run without arguments to see a list of available command categories:

zun-status

Categories are:

upgrade

Detailed descriptions are below:

You can also run with a category argument such as upgrade to see a list of all commands in that category:

zun-status upgrade

These sections describe the available categories and arguments for zun-status.

Upgrade

zun-status upgrade check

Performs a release-specific readiness check before restarting services with new code. For example, missing or changed configuration options, incompatible object states, or other conditions that could lead to failures while upgrading.

Return Codes

Return code	Description
0	All upgrade readiness checks passed successfully and there is nothing to do.
1	At least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK.
2	There was an upgrade status check failure that needs to be investigated. This should be considered something that stops an upgrade.
255	An unexpected error occurred.

History of Checks

3.0.0 (Stein)

Sample check to be filled in with checks as they are added in Stein.

1.9 KiB Raw Blame History