Red Hat Bugzilla – Bug 924531
support iSCSI boot in UEFI mode machine
Last modified: 2014-06-09 13:45:14 EDT
Created attachment 714234 [details] attached Screenshot for noavailableRHEVHyperisor.png Description of problem: Auto install RHEV-H with follow parameters in UEFI mode machine. BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2013-02.com:hadong iscsi_install iscsi_server=10.66.11.102:3260 firstboot After auto install success, then boot rhev-h in UEFI mode machine, but no available RHEV Hyperisor to boot.(Seen noavailableRHEVHyperisor.png) Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130318.1.el6_4 How reproducible: 100% Steps to Reproduce: 1.Auto install rhev-h with with "BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2013-02.com:hadong iscsi_install iscsi_server=10.66.11.102:3260 firstboot" parameter Actual result: Expect result:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Created attachment 814870 [details] attached ovirt.log
Test version: ovirt-node-3.0.1-9.el6_5.noarch.rpm rhevh-6.5-20131213.0.0.iso Test as follow: Auto install RHEV-H with follow parameters in UEFI mode machine. BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2013-02.com:hadong iscsi_install iscsi_server=10.66.11.127:3260 firstboot After auto install success, then boot rhev-h in UEFI mode machine success. so this bug has been fixed, after the status changed into "ON_QA",i'll verify it.
According to comment 10, change the status into "verified".
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thank you for your help.
Hi could you let me know what the problem was and what the fix was for the doc text? Thanks.
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. http://rhn.redhat.com/errata/RHBA-2014-0033.html