openstack/ironic
Code Issues Proposed changes

Document that nova-compute attaches VIF to active nodes on start up

Browse Source 
This can break upgrades if nova-compute is restarted while all
ironic-conductor processes are down. Let us add a warning to
the upgrade documentation.

Change-Id: I914ca0b096f1b320decac9103269afec79ac21f8
This commit is contained in:
Dmitry Tantsur 2018-06-18 15:24:41 +02:00
parent c8affbd485
commit 0b408131a7
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/admin/upgrade-guide.rst
View File

@ -301,6 +301,13 @@ release.
* Upgrade ``python-ironicclient`` along with other services connecting * Upgrade ``python-ironicclient`` along with other services connecting
to the Bare Metal service as a client, such as ``nova-compute``. to the Bare Metal service as a client, such as ``nova-compute``.
.. warning::
A ``nova-compute`` instance tries to attach VIFs to all active instances
on start up. Make sure that for all active nodes there is at least one
running ``ironic-conductor`` process to manage them. Otherwise the
instances will be moved to the ``ERROR`` state on the ``nova-compute``
start up.
* Run the ``ironic-dbsync online_data_migrations`` command to make sure * Run the ``ironic-dbsync online_data_migrations`` command to make sure
that data migrations are applied. The command lets you limit that data migrations are applied. The command lets you limit
the impact of the data migrations with the ``--max-count`` option, which the impact of the data migrations with the ``--max-count`` option, which