openstack
/
nova
Code Issues Proposed changes
nova/doc
History
Matt Riedemann df2845308d Change nova-manage unexpected error return code to 255 
If any nova-manage command fails in an unexpected way and
it bubbles back up to main() the return code will be 1.
There are some commands like archive_deleted_rows,
map_instances and heal_allocations which return 1 for flow
control with automation systems. As a result, those tools
could be calling the command repeatedly getting rc=1 thinking
there is more work to do when really something is failing.

This change makes the unexpected error code 255, updates the
relevant nova-manage command docs that already mention return
codes in some kind of list/table format, and adds an upgrade
release note just to cover our bases in case someone was for
some weird reason relying on 1 specifically for failures rather
than anything greater than 0.

Change-Id: I2937c9ef00f1d1699427f9904cb86fe2f03d9205
Closes-Bug: #1840978
 		2019-08-21 17:03:11 -04:00
..
api_samples API microversion 2.76: Add 'power-update' external event 2019-08-15 13:19:44 -04:00
ext Replace support matrix ext with common library 2018-07-16 15:04:00 +01:00
notification_samples Merge "Enhance service restart in functional env" 2019-06-27 17:50:19 +00:00
source Change nova-manage unexpected error return code to 255 2019-08-21 17:03:11 -04:00
test docs: Rework all things metadata'y 2019-06-20 18:22:34 +01:00
README.rst Update api-ref location 2019-07-22 19:17:28 +02:00
requirements.txt tox: Keeping going with docs 2019-07-18 10:26:15 +01:00

README.rst

OpenStack Nova Documentation README

Both contributor developer documentation and REST API documentation are sourced here.

Contributor developer docs are built to: https://docs.openstack.org/nova/latest/

API guide docs are built to: https://docs.openstack.org/api-guide/compute/

For more details, see the "Building the Documentation" section of doc/source/contributor/development-environment.rst.