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.
Red Hat Enterprise Linux Atomic Host 7.1.0 offers iSCSI support during Anaconda installation, but the current content set does not include iSCSI support, so the system will not be able to access the storage. Choosing this option in the installer is not recommended.
Created attachment 988460[details]
rdsosreport.txt
Description of problem:
RHEL Atomic host is unable to boot when the destination hard drives are composed of local drives and iSCSI drives.
Version-Release number of selected component (if applicable):
anaconda 19.31.79-1
RHEL Atomic Host 20150129.0
How reproducible:
always
Steps to Reproduce:
1. Prepare a machine with at least one local hard drive connected to network with iSCSI targets
2. Start installation
3. Add iSCSI targets
4. Select local hard drive and at least one iSCSI target
5. Finish the installation, reboot
Actual results:
Host is unable to boot, it ends in dracut's emergency shell.
Expected results:
Host boots up
Additional info:
rdsosreport.txt attached with rd.debug turned on
Kernel command line:
BOOT_IMAGE=/ostree/rhel-atomic-host-5dfb4e57904b41f15d098be05bcc6b80feedf3961c1f916f18daffcd2e8d5058/vmlinuz-3.10.0-227.el7.x86_64 netroot=iscsi:@10.0.0.1::3260::iqn.2010-04.virt.nap:default netroot=iscsi:@10.0.0.1::3260::iqn.2010-04.virt.nap:second vconsole.keymap=us iscsi_initiator=iqn.1994-05.com.redhat:933d2fb45553 rd.lvm.lv=rah_system1/swap rd.lvm.lv=rah_system1/root crashkernel=auto vconsole.font=latarcyrheb-sun16 ifname=eth0:52:54:00:12:34:56 ip=eth0:dhcp root=/dev/mapper/rah_system1-root ostree=/ostree/boot.0/rhel-atomic-host/5dfb4e57904b41f15d098be05bcc6b80feedf3961c1f916f18daffcd2e8d5058/0 console=ttyS0 rd.debug
ifname=eth0:52:54:00:12:34:56 should never be on the kernel command line.
try "ifname=myeth0:52:54:00:12:34:56 ip=myeth0:dhcp"
Nevertheless, the initramfs of the atomic host does not seem to have iSCSI support.
Hi Milan,
This commit in the 7.1_BETA branch of the Release Notes contains the description from the Doc Text field:
bfdca07 Added 4 Known Issues for Atomic.
Thanks.
Colin Walters, can we reassign this bug to something else than dracut? Clearly, it is not the fault of dracut, that the atomic host has no support for iSCSI.
Created attachment 988460 [details] rdsosreport.txt Description of problem: RHEL Atomic host is unable to boot when the destination hard drives are composed of local drives and iSCSI drives. Version-Release number of selected component (if applicable): anaconda 19.31.79-1 RHEL Atomic Host 20150129.0 How reproducible: always Steps to Reproduce: 1. Prepare a machine with at least one local hard drive connected to network with iSCSI targets 2. Start installation 3. Add iSCSI targets 4. Select local hard drive and at least one iSCSI target 5. Finish the installation, reboot Actual results: Host is unable to boot, it ends in dracut's emergency shell. Expected results: Host boots up Additional info: rdsosreport.txt attached with rd.debug turned on