Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
System with rootfs on iSCSI fails to boot:
...
connection2:0: detected conn error (1020)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.org.linux-iscsi:test, portal: 192.168.122.87,3260].
iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals
Version-Release number of selected component (if applicable):
RHEL-8.0-20190107.n.0
dracut-049-8.git20181030.el8
iscsi-initiator-utils-6.2.0.876-6.gitf3c8e90.el8
systemd-239-10.el8
How reproducible:
always
Steps to Reproduce:
1. Create an iSCSI target (used RHEL-8 with targetcli)
# yum install -y targetcli
# systemctl start target
# systemctl enable target
# dd if=/dev/zero of=disk bs=1 count=1 seek=6G
# targetcli
cd /backstores/fileio
create file_or_dev=/root/disk name=disk
cd /iscsi
create wwn=iqn.2003-01.org.linux-iscsi:test
cd iqn.2003-01.org.linux-iscsi:test/tpg1/luns
create /backstores/fileio/disk
cd ../acls
create iqn.2005-03.org.open-iscsi:client
cd /
saveconfig
2. run installation, use the iSCSI disk created above for rootfs. Place /boot and swap on local disk (not using LVM)
3. finish the installation and restart the system
Actual results:
System will not boot
Expected results:
System boots successfully
Additional info:
iSCSI target reports:
Jan 07 16:41:02 localhost.localdomain kernel: iSCSI Initiator Node: iqn.1994-05.com.redhat:8a58a275417f is not authorized to access iSCSI target portal group: 1.
Jan 07 16:41:02 localhost.localdomain kernel: iSCSI Login negotiation failed.
This looks suspicious, since the initiator name should be set to "iqn.2005-03.org.open-iscsi:client" (rd.iscsi.initiator=iqn.2005-03.org.open-iscsi:client is present on the kernel cmdline)
Should there be an 8.0 Release Note for this?
Does this effect all such installations? (Don't we test this on each build/release? Why was it not found until Jan.?)
Is there a work-around we can document for people to use in 8.0?
Should this be fixed in the z-stream?
Tom
(In reply to Tom Coughlan from comment #7)
> Should there be an 8.0 Release Note for this?
My understanding is that the python-blivet change (bug 1664587) was sufficient to work around the dracut problem, so that customers will not see the problem even though the dracut fix will not land until 8.1.
Reproduced with dracut-049-10.git20190115.el8.
Verified with dracut-049-13.git20190614.el8, the rd.iscsi.initiator= parameter on the kernel command line is preferred over the value of the initiator name stored in the initrd.
Moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3604