openstack/ironic
Code Issues Proposed changes

Merge "docs: cover what happens if someone changes iscsi passwords"

Browse Source
This commit is contained in:
Zuul
2025-11-04 22:33:18 +00:00
committed by Gerrit Code Review
parent d9fc068630 d59ad9f82d
commit 9305e273a8
2 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/boot-from-volume.rst
View File

@@ -95,6 +95,14 @@ on an existing node::
A default storage interface can be specified in ironic.conf. See the
`Conductor Configuration`_ section for details.
The storage interface is responsible for managing the mapping state of the
volume to the host. If some changes need to be communicated from Cinder and
then updated for Ironic to become aware of them, such as a change in iSCSI
credentials, then the act of powering baremetal node off via Ironic's API
will trigger these values to be updated automatically as the ``cinder``
storage interface resets the volume attachments with power actions to
ensure the latest information is used for each boot sequence.
iSCSI Configuration
-------------------
In order for a bare metal node to boot from an iSCSI volume, the ``iscsi_boot``

20
doc/source/admin/troubleshooting.rst
View File

@@ -1504,3 +1504,23 @@ navigate the issue you have encountered.
Unfortunately, there is no magical quick fix for these sorts of issues, but
the Ironic community has a track record of attempting to navigate and address
these issues as they arise.
I'm using Boot-From-Volume, and the SAN passwords were changed.
===============================================================
In this event, the credential uses for an iSCSI attachment have been changed
on a storage area network (SAN), and Ironic nodes have lost connectivity with
iSCSI boot volumes.
The proper procedure here varies based upon if you're using the ``cinder``
``storage_interface`` option, or if you're using the ``external`` option.
In the case of the ``cinder`` driver being used, if you power off the
baremetal node via Ironic's API, and then power the node back on. This
will trigger Ironic to attempt to re-attach the volume to the baremetal
node via Cinder's API which will cause the most up-to-date configuration
to be presented to the bare metal node being booted.
If you're using the ``external`` interface option, you will need to manually
reset you're volume connector information values. Please refer to
:doc:`/admin/boot-from-volume` for more information.