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:
hit this issue when testing the SAN boot.
this issue is blocking our SAN boot testing.
RHEL-7.0-20140313.n.0
anaconda-19.31.67-1.el7.x86_64.rpm
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. press 'add a disk' in the specialized network & disk table.
2. configuring some FC/FCoE luns in anaconda
3. try to select the lun as the boot disk
Actual results:
fail to select the checkbox.
Expected results:
Additional info:
(In reply to David Shea from comment #5)
> Attach the logs from /tmp to this bug.
David,
we have the existing node to reproduce this issue. and I have provided the reproducer in this log. This is blocking our SAN boot feature and impact many vendor and customer. Also it is obviously a regression bug.
considering the RHEL 7.0 is going to RC, we hope it will be fixed ASAP.
I have loaded you my node https://beaker.engineering.redhat.com/view/storageqe-05.rhts.eng.bos.redhat.com to you.
for all logs please see the job https://beaker.engineering.redhat.com/jobs/611826
1. open the above beaker page and go to the 'Provision' Page
2. select the RHEL-7.0-20140313.n.0 tree
3. override the KickStart MetaData with !ignoredisk manual' to install the OS manually
4. add 'vnc' to Kernel Options (Install) to use vnc for installation
5. after the anaconda starts and the vncserver starts, please follow the vnc link to access to the node with vnc. usually
vncview storageqe-18.rhts.eng.bos.redhat.com:1
6. Select the Installation Destination then press 'Add disk' in the 'Specialized network & storage' table.
7. you will see some multipath disks, try to select one mpath disk as the boot disk, but you will see the checkbox does not work.
Thanks,
Xiaowei Li
(In reply to Xiaowei Li from comment #6)
> (In reply to David Shea from comment #5)
> > Attach the logs from /tmp to this bug.
> > 5. after the anaconda starts and the vncserver starts, please follow the vnc
> link to access to the node with vnc. usually
> vncview storageqe-18.rhts.eng.bos.redhat.com:1
for the loaned node ,it's vncview storageqe-05.rhts.eng.bos.redhat.com:1