From 5a75e9afbbf9d2710ac4ff19b8472fbf708a2fe1 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Tue, 7 May 2024 10:31:34 -0700 Subject: [PATCH] docs: detail limitation of use of config drive + rebuild Change-Id: I2054d6a87d7dcf74004d3404c73e39a100f1fe9b --- doc/source/admin/troubleshooting.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/source/admin/troubleshooting.rst b/doc/source/admin/troubleshooting.rst index 62e24f5196..9bccd7efb8 100644 --- a/doc/source/admin/troubleshooting.rst +++ b/doc/source/admin/troubleshooting.rst @@ -1239,3 +1239,23 @@ If your bare metal management processes require that full machine management is made using a project scoped account, please configure an appropriate node ``owner`` for the nodes which need to be managed. Ironic recognizes this is going to vary based upon processes and preferences. + +Config Drives in Swift, but rebuilds fails? +=========================================== + +When deploying instances, Ironic can be configured such that configuration +drives are stored in Swift. The pointer to the configuration drive is saved +in Ironic as a Temporary URL which has a time expiration. + +When you issue the rebuild request for a node, Ironic expects that you will +supply new configuration drive contents with your request, however this is +also optional. + +Because Swift has been set as the optional configuration drive storage +location, a rebuild can fail if the prior configuration drive file is no +longer accessible and no new configuration drive has been supplied to Ironic. + +To resolve this case, you can either supply new configuration drive contents +with your request, or disable configuration from being stored in Swift for +new baremetal node deployments by changing setting +``[conductor]configdrive_use_object_store`` to ``false``.