Red Hat Bugzilla – Bug 956568
Auto install RHEV-H failed with "storage_init=ata:ALL" parameter.
Last modified: 2014-01-21 14:32:02 EST
Created attachment 739727 [details] attached the ovirt.log Description of problem: Auto install RHEV-H failed with "storage_init=ata:ALL" parameter. G Welcome to Red Hat Enterprise Virtualization Hypervisor Starting udev: G[ OK ] Setting hostname localhost.localdomain: [ OK ] Alternate GPT is invalid, using primary GPT. .... Starting sshd: [ OK ] Starting ksm: [ OK ] Starting ksmtuned: [ OK ] Starting crond: [ OK ] Starting rhsmcertd...[ OK ] Starting wdmd: [ OK ] Starting ovirt-post: [ OK ] Starting virt-who: [ OK ] Starting ovirt-cim: [ OK ] Starting ovirt-firstboot: Performing automatic disk partitioning Configuring Network Automatic installation failed. Please review /var/log/ovirt.log Apr 25 02:04:12 Automatic installation failed. Please review console messages. Apr 25 02:04:12 Press Enter to drop to emergency shell. Maybe the root cause happens in "find_disk()" of bash script "/usr/share/dracut/modules.d/91ovirtnode/ ovirt-boot-functions". There was only one disk "/dev/sda" on localhost, But after execute "find_disk "ata" "ALL"", it return "/dev/sda,/dev/sda", actually we want it return "/dev/sda" Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130415.0.el6_4 How reproducible: 100% Steps to Reproduce: 1.Auto install rhev-h with with "BOOTIF=eth0 storage_init=ata:ALL firstboot" parameter Actual result: After Step 1, Auto install RHEV-H failed with "storage_init=ata:ALL" parameter Expect result: Auto install RHEV-H success with "storage_init=ata:ALL" parameter Additional info:
Created attachment 753766 [details] attached the ovirt.log Using the auto iso "rhev-hypervisor6-6.4-20130501.0.auto623.el6_4.iso" to try follow case: BOOTIF=eth0 storage_init=ata:ALL firstboot Failed install with follow error info: Welcome to Red Hat Enterprise Virtualization Hypervisor Starting udev: G[ OK ] .......... Starting ntpd: [ OK ] Starting ksm: [ OK ] Starting ksmtuned: [ OK ] Starting crond: [ OK ] Starting rhsmcertd...[ OK ] Starting wdmd: [ OK ] Starting ovirt-post: [ OK ] Starting virt-who: [ OK ] Starting ovirt-cim: [ OK ] Starting ovirt-firstboot: Performing automatic disk partitioning ERROR:ovirtnode.storage:HostVG/AppVG exists on a separate disk ERROR:ovirtnode.storage:Manual Intervention required Configuring Network Automatic installation failed. Please review /var/log/ovirt.log May 28 07:14:58 Automatic installation failed. Please review console messages. May 28 07:14:58 Press Enter to drop to emergency shell. bash: no job control in this shell [root@dhcp-10-111 /]# But auto install with "BOOTIF=eth0 storage_init=/dev/sda firstboot" success,no similar issue
Cannot reproduce on current 6.5 images. An upstream fix for a different, but related problem appears to have also fixed this. Is this still producible?
(In reply to Ryan Barry from comment #5) > Cannot reproduce on current 6.5 images. An upstream fix for a different, but > related problem appears to have also fixed this. Is this still producible? Seem that after the patch http://gerrit.ovirt.org/#/c/17477/ has been merged and couldn't reproduce this issue on current 6.5 images. But the "find_disk()" return value issue didn't have been fixed in bash script "/usr/share/dracut/modules.d/91ovirtnode/ ovirt-boot-functions". There was only one disk "/dev/sda" on localhost, But after execute "find_disk "ata" "ALL"", it return "/dev/sda,/dev/sda", actually we want it return "/dev/sda" Append patch http://gerrit.ovirt.org/#/c/19908/ in here to fix find_disk return value issue.
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 auto install with "BOOTIF=eth0 storage_init=ata:ALL firstboot" success Also after execute "/usr/share/dracut/modules.d/91ovirtnode/ ovirt-boot-functions find_disk "ata" "ALL"" it return "/dev/sda", so this bug has been fixed, 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 Thanks in advance.
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