-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.0.0
-
anaconda-34.25.4.2-1.el9
-
None
-
Important
-
rhel-sst-installer
-
16
-
20
-
None
-
QE ack, Dev ack
-
False
-
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
Description of problem:
When booting the installer, a 'hostnqn' file is created. The hostnqn should be generated using the UUID of the host system, however it currently is not.
Version-Release number of selected component (if applicable):
Testing on RHEL 9 Nightly build from January 28, 2022
How reproducible:
Very
Steps to Reproduce:
1. Boot nightly ISO to graphical installer
2. Switch to a console
3. Read the hostnqn ($ cat /etc/nvme/hostnqn) and compare it to the hostnqn that is expected ($ nvme gen-hostnqn)
Actual results:
The hostnqn is not the same as what the nvme utility generates
Expected results:
The hostnqn should be the same as what is generated by the nvme utility
Additional info:
Before the graphical installer begins, a couple things should happen in order to NVME Boot From SAN devices to be discovered automatically:
1. the correct NQN should be generated using 'nvme' utility:
nvme gen-hostnqn > /etc/nvme/hostnqn
2. NVME Discovery should be initiated:
echo add > /sys/class/fc/fc_udev_device/nvme_discovery
3. The NQN and Host ID files should be copied to sysimage so that the files get included by dracut
cp /etc/nvme/hostnqn /mnt/sysimage/etc/nvme/hostnqn
cp /etc/nvme/hostid /mnt/sysimage/etc/nvme/hostnqn
Following these three steps will enable automatic discovery of NVMe devices
- is blocked by
-
RHEL-8041 %post script is incompatible with image-based updates (e.g. ostree)
- Planning
- external trackers
- links to
-
RHBA-2023:125629 anaconda bug fix and enhancement update