openstack/cinder
Code Issues Proposed changes
cinder/doc/source/cli/cinder-status.rst
Jay S. Bryant bc18906f01 Add upgrade check for Windows iSCSI driver. 
The WindowsDriver was renamed in the Queens release to
WindowsISCSIDriver to avoid confusion with the SMB driver.
The backwards compatibility for this has now been removed, so
any cinder.conf settings still using
cinder.volume.drivers.windows.windows.WindowsDriver
must now be updated to use
cinder.volume.drivers.windows.iscsi.WindowsISCSIDriver.

The change includes the addtion of a function to get the
enabled_drivers for a system as it is likely that the
functionality will be useful for multiple update checks
in the future.

Change-Id: I34038c847b75f9f9bd1c4dd4d9a5803cd66ffc8d
2019-05-23 11:38:58 -05:00

2.8 KiB
Raw Blame History

cinder-status

CLI interface for cinder status commands

Author

openstack@lists.openstack.org

Copyright

OpenStack Foundation

Manual section

1

Manual group

cloud computing

Synopsis

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

Description

cinder-status is a tool that provides routines for checking the status of a Cinder deployment.

Options

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

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

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

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

cinder-status upgrade

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

Upgrade

cinder-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 the database. It may also make requests to other services' REST API via the Keystone service catalog.

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

14.0.0 (Stein)

  • Check added to ensure the backup_driver setting is using the full driver class path and not just the module path.
  • Checks for the presence of a policy.json file have been added to warn if policy changes should be present in a policy.yaml file.
  • Ensure that correct volume_driver path is used for Windows iSCSI driver.

15.0.0 (Train)

  • Check added to make operators aware of new finer-grained configuration options affecting the periodicity of various Cinder tasks. Triggered when the the periodic_interval option is not set to its default value.
  • Added check for use of deprecated cinder.quota.NestedDbQuotaDriver.

See Also

Bugs