From 0b408131a751b65af553d727a89443cec21fd58e Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Mon, 18 Jun 2018 15:24:41 +0200 Subject: [PATCH] Document that nova-compute attaches VIF to active nodes on start up 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 --- doc/source/admin/upgrade-guide.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/source/admin/upgrade-guide.rst b/doc/source/admin/upgrade-guide.rst index 14e3834d41..42f2b2718d 100644 --- a/doc/source/admin/upgrade-guide.rst +++ b/doc/source/admin/upgrade-guide.rst @@ -301,6 +301,13 @@ release. * Upgrade ``python-ironicclient`` along with other services connecting 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 that data migrations are applied. The command lets you limit the impact of the data migrations with the ``--max-count`` option, which