Created attachment 1075785 [details] screenshot of enter to dracut Description of problem: Auto-install with wrong BOOTIF parameter enter to dracut, and if field in "exit" on the shell, install can continue and install successfully. Version-Release number of selected component (if applicable): rhev-hypervisor-7-7.1-20150917.0.e17ev ovirt-node-3.2.3-20.el7.noarch dracut-033-241.el7_1.5.x86_64 How reproducible: 100% Steps to Reproduce: 1. Auto install RHEVH with the follow parameters. BOOTIF=em2 storage_init=/dev/sda adminpw=OKr05SbCu3D3g firstboot (note:actually there is no em2 on machine) Actual results: After step1, enter to dracut(such as screenshot in attach), and if field in "exit" on the shell, install can continue and install successfully. Expected results: After step1, auto install should enter to shell with prompt message due to wrong BOOTIF parameter, and can not continue installation. Additional info:
Created attachment 1075789 [details] rdsosreport.txt
Adjusting priorities, because this is an unusual flow, and has no impact on runtime, it just prevents auto-install.
*** Bug 1264049 has been marked as a duplicate of this bug. ***
Adjusting priorities, because encounter this issue on rhev-hypervisor-7-7.2-20151009.0.e17ev, and auto-install with usual kernel arguments: BOOTIF=link storage_init=/dev/sda adminpw=OKr05SbCu3D3g firstboot
RHEV-H is behaving like RHEL, thus I am closing this bug. If oyu think this is an issue, please open a bug against platform dracut and describe the expected behavior.
(In reply to Huijuan Zhao from comment #4) > Adjusting priorities, because encounter this issue on > rhev-hypervisor-7-7.2-20151009.0.e17ev, and auto-install with usual kernel > arguments: > > BOOTIF=link storage_init=/dev/sda adminpw=OKr05SbCu3D3g firstboot BOOTIF=link does not work on RHEV-H 7, this is a known limitation. Please either use the macaddr or the nic name.