From 4417725f0e1885ae40b937e6a7406ebaad98e9a4 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Wed, 4 Dec 2024 11:25:40 -0500 Subject: [PATCH] faq: add more info about multipath + iSCSI This came up in a customer case. AFAICT, we can't really rely on iBFT for this because it doesn't contain information about all the paths. See also: https://issues.redhat.com/browse/OCPBUGS-42736 --- docs/faq.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index 4b177c9c..3743741f 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -336,6 +336,17 @@ the target device is multipathed. (And e.g. if using iPXE, you likely would then also want to specify all the paths to the `sanboot` command in your iPXE script, see e.g. [this test config](https://github.com/coreos/coreos-assembler/blob/8a354045c68e5dce8cd5736dc6fdcfac1d603b35/mantle/cmd/kola/resources/iscsi_butane_setup.yaml#L70-L71).) +Similarly to the above, in the custom initiation case you need to add the +`rd.iscsi.initiator` and `netroot` kargs. Specify as many `netroot` kargs as +there are paths, e.g.: + +``` +coreos-installer --append-karg rd.iscsi.initiator=iqn.2023-11.coreos.diskless:testsetup \ + --append-karg netroot=iscsi:10.0.2.15::::iqn.2023-10.coreos.target.vm:coreos \ + --append-karg netroot=iscsi:10.0.2.16::::iqn.2023-10.coreos.target.vm:coreos \ + --append-karg rd.multipath=default +``` + ## Q: How do I configure a secondary block device via Ignition/MC if the name varies on each node? First, verify that there isn't a `/dev/disk/by-*` symlink which works for your needs. If not, a few approaches exist: