View Issue Details

IDProjectCategoryView StatusLast Update
0007873CentOS-7dracutpublic2014-11-12 15:44
Reporterjmsq Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
OSCentOSOS Version7 
Product Version7.0-1406 
Summary0007873: PXEBoot NetInstall Fails Without Useful Error Message
DescriptionSo I stumbled upon this bug when creating a PXE Boot Network Installer for our infrastructure on CentOS 7. The relevant boot line looks like this:

KERNEL vmlinuz-centos7
APPEND initrd=initrd-centos7.img inst.ks=http://xxxxx/ks-centos7.cfg inst.sshd nameserver=x.x.x.x ip=x.x.x.x::x.x.x.1:255.255.240.0:installer:eno1:none

If you incorrectly specify the interface for static configuration to one that doesn't exist, for example eth0, the boot will fail despite the fact that the correct interface was configured via DHCP and was able to download the kickstart and various files.

I realize that this is probably desired behavior; however my problem with this is the error message I got:

dracut-initqueue: Warning: Could not boot.

With no other indication whatsoever of why it refused to boot. I finally found the fix through a good deal of trial and error. Before anyone asks why I didn't do rd.debug, I did, but it produced so much useless output that any chance of finding what went wrong was lost in the noise. If dracut is going to warn that it couldn't not boot, it needs to provide an error code or something else useful for knowing why, without turning on full-verbosity debugging.
Steps To ReproduceSetup PXE Installer.

Set ip= line to an interface that doesn't exist.

Watch the boot fail without any useful error messages.
TagsNo tags attached.
abrt_hash
URL

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2014-11-12 15:44 jmsq New Issue