Hide Forgot
Created attachment 791632 [details] ovirt.log from /tmp Description of problem: I'm trying to install ovirt-node ovirt-node-iso-3.1.0-0.999.5.vdsm.fc19.iso onto an IBM xserver 3650 M3 without any success. I got an error " Exception: RuntimeError('Failed to set install bootloader' ,) " when installer try to set the bootloader. Version-Release number of selected component (if applicable): ovirt-node ovirt-node-iso-3.1.0-0.999.5.vdsm.fc19.iso How reproducible: boot from CD, reply to all questions and wait for Exception. Actual results: Exception: RuntimeError('Failed to set install bootloader' ,) Expected results: a success ovirt installation Additional info: log files
Created attachment 791633 [details] ovirt.log from /var/log
Created attachment 791634 [details] ovirt-node.log
I've tried this build http://jenkins.ovirt.org/job/node-devel/distro=fedora19/373/ and the problem remain present.
Test version: ovirt-node-iso-3.1.0-0.999.5.vdsm.fc19.iso Test machine: ibm-x3650m3-01 Dell 990 I'm trying to install above build onto IBM x3650 M3 server still fail. I am also do the same testing on Dell 990 and fail again. The error info as following: dracut-initqueue[258]: Warning: Could not boot. dracut-initqueue[258]: Warning: /dev/disk/by-label/ovirt-node-image does not exist dracut-initqueue[258]: Warning: /dev/mapper/live-rw does not exist Seem the error info same as Bug 967750 - Install issue via CD-ROM. Thanks!
Here is the command that I used when launching the install process to avoid the Bug 967750. kernel /isolinux/vmlinuz0 append initrd=/isolinux/initrd0.img root=live:/dev/sr0 rootfstype=auto ro liveimg rd.live.check rootflags=ro crashkernel=128M elevator=deadline install rhgb quiet rd.lvm=0 rd.luks=0 rd.md=0 rd.dm=0 Thanks!
(In reply to mpaupe from comment #5) > Here is the command that I used when launching the install process to avoid > the Bug 967750. > > kernel /isolinux/vmlinuz0 > append initrd=/isolinux/initrd0.img root=live:/dev/sr0 rootfstype=auto ro > liveimg rd.live.check rootflags=ro crashkernel=128M elevator=deadline > install rhgb quiet rd.lvm=0 rd.luks=0 rd.md=0 rd.dm=0 > > Thanks! Yes, this time I append root=live:/dev/sr0 to kernel command can install successful. Thank you for your advice.
(In reply to shaochen from comment #6) > (In reply to mpaupe from comment #5) > > Here is the command that I used when launching the install process to avoid > > the Bug 967750. > > > > kernel /isolinux/vmlinuz0 > > append initrd=/isolinux/initrd0.img root=live:/dev/sr0 rootfstype=auto ro > > liveimg rd.live.check rootflags=ro crashkernel=128M elevator=deadline > > install rhgb quiet rd.lvm=0 rd.luks=0 rd.md=0 rd.dm=0 > > > > Thanks! > > Yes, this time I append root=live:/dev/sr0 to kernel command can install > successful. > Thank you for your advice. Witch ovit-node version did you use ? Some hardway specific setting are requiered?
> Witch ovit-node version did you use ? Some hardway specific setting are > requiered? Test version: ovirt-node-iso-3.1.0-0.999.5.vdsm.fc19.iso Test machine: ibm-x3650m3-01 (intel cpu + 48G Mem) Install above build on ibm-x3650m3-01 via TUI can successful. I upload the successful screen for you reference.
Created attachment 792084 [details] successful
Thanks for the result you were lucky ;-) Would it be possible to get more details about you efi config ? Am going to build an iso with the debug option later next week. Thanks
(In reply to mpaupe from comment #10) > Thanks for the result you were lucky ;-) > > Would it be possible to get more details about you efi config ? > > Am going to build an iso with the debug option later next week. > > Thanks OK, but I test this build with legacy mode but no efi mode. steps: 1. attach virtual media. 2. set CDROM as the first boot. 3. Choose legacy option (it will boot from virtual media). I can provide the remote access for you connect if you need.
Hey Checn, can you please check if this problem still exists with 3.0.3?
*** Bug 967750 has been marked as a duplicate of this bug. ***
(In reply to Fabian Deutsch from comment #12) > Hey Checn, > > can you please check if this problem still exists with 3.0.3? Test version: ovirt-node-iso-3.0.3-1.1.fc19.iso Test machine: ibm-x3650m3-01 Dell 990 Install above build onto IBM x3650 M3 server still fail, please see attachment for more details. But it can successful with Dell 990.
Created attachment 830481 [details] dracut error
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Hey Chen, does this bug still happen with 3.0.4?
(In reply to Fabian Deutsch from comment #17) > Hey Chen, > > does this bug still happen with 3.0.4? Test version: ovirt-node-iso-3.4-20140423.1.el6.iso (download link: http://resources.ovirt.org/pub/ovirt-3.4/iso/) ovirt-node-hypervisor 3.0.4(1.0.201401291204.el6) ovirt-node-3.0.4-1.0.el6.noarch Test machine: ibm-x3650m3-01 Test result: 1. Install above build on ibm-x3650m3-01 via TUI can successful. 2. Reboot pass. 3. Login pass.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed. If this is a blocker please add it to the tracker Bug #1095370
mpaupe, Can you try a recent build and see if the problem persists?
This is an automated message: oVirt 3.4.2 has been released. This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
closing, if this still occurs on current version please reopen