What were you trying to do that didn't work?

The issue was observed in a customer case — when installing an iSCSI-booted cluster using Assisted Installer, the original boot-time IQN was not stored in /etc/iscsi/initiatorname.iscsi, causing issues until it was manually updated.

What is the impact of this issue to you?

The customer reported that the worker nodes would core dump and enter a reboot loop until the IQN in /etc/iscsi/initiatorname.iscsi was manually changed to the original IQN.

How reproducible is this bug?:

always

Steps to reproduce

1. boot from iPXE first time and set initiator
2. once the node comes up, a different initiator observed:

[root@test-infra-cluster-f9ac0f2a-worker-0 core]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:76a91e8e2699

[root@test-infra-cluster-f9ac0f2a-worker-0 core]# cat /sys/firmware/ibft/initiator/initiator-name
iqn.2024-11.com.example:dummy

Expected results

use the iqn value from iBFT

Actual results

generates new iqn