openstack/ironic
Code Issues Proposed changes
e13f593f37
ironic/doc/source/cli/ironic-status.rst
Dmitry Tantsur bb4cd9ea78
Upgrade check on removed or deprecated hardware types and interfaces 
Issues an error on removed items still used in the configuration.

Issues a warning on deprecated items or nodes that use removed drivers
or interfaces.

Change-Id: Iebb4cd611f7111cde20acf9ba3d4c9127925b6cf
Closes-Bug: #2051954
2024-07-01 15:44:23 +02:00

2.0 KiB
Raw Blame History

ironic-status

Synopsis

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

Description

ironic-status is a tool that provides routines for checking the status of a Ironic deployment.

Options

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

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

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

ironic-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:

ironic-status upgrade

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

Upgrade

ironic-status upgrade check

Performs a release-specific readiness check before restarting services with new code. This command expects to have complete configuration and access to databases and services.

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

12.0.0 (Stein)

  • Adds a check for compatibility of the object versions with the release of ironic.

Wallaby

  • Adds a check to validate the configured policy file is not JSON based as JSON based policies have been deprecated.

2024.2

  • Adds a check that hardware types and interfaces in the configuration exist, and that nodes are configured with existing drivers and interfaces.