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:
iSCSI BFS LUN does not show up in anaconda if local HD is present
Version-Release number of selected component (if applicable):
SS4 image, anaconda-19.31.51-1
How reproducible:
multiple systems, 100% of the time
Steps to Reproduce:
1. Have local HD present
2. Configure Broadcom boot rom to log into iSCSI target
3. Start the installation from the CD
4. Once in GUI, notice that the iSCSI LUN is not shown as an available disk. When going to ttyS2, notice that the target is logged in.
5. Repeat the above steps with the local HD removed. The iSCSI LUN will show in the GUI as an available disk to install to.
Actual results:
Unable to install to iSCSI LUN if local HD is present
Expected results:
Able to install to iSCSI LUN even if local HD is present
Additional info:
- Logs attached for both working(no local HD present) and failing(local HD present) cases.
Isn't the problem the iSCSI disk just not being selected by default in non-working case because local HD is selected? In this case you need to go to Specialzed & Network Disks (click [Add a disk]) and then check the disk in advanced storage screen so that the disk is visible and selectable in Device Selection screen.
(In reply to Radek Vykydal from comment #4)
> Isn't the problem the iSCSI disk just not being selected by default in
> non-working case because local HD is selected? In this case you need to go
> to Specialzed & Network Disks (click [Add a disk]) and then check the disk
> in advanced storage screen so that the disk is visible and selectable in
> Device Selection screen.
You are absolutely correct. Just checked again and the iSCSI disk does show up when drilling down a little further. The confusion must've been while we were troubleshooting an earlier snapshot which needed extra kernel parameters and were having trouble getting the disk to appear during installation. Not an issue... closing.