Description of problem: I'm using a network root fs from iscsi device. The /boot been in a compact flash. System is installed with kickstart from f17 GA. Since some update I cannot network-boot anymore unless I using runlevel 1 Version-Release number of selected component (if applicable): NetworkManager-0.9.4.0-9.git20120521.fc17.i686 dracut-network-018-98.git20120813.fc17.noarch How reproducible: always with network root. Reproduced twice with a new installation. Steps to Reproduce: 1. Install f17 on remote iscsi device 2. yum update to current Actual results: It fails to boot properly. the boot process stop after NetworkManager is activated. Expected results: It should boot properly Additional info: Initial configuration. # Generated by dracut initrd DEVICE=em1 ONBOOT=yes NETBOOT=yes UUID=6dfb0b9d-8b69-4096-8b81-6edde4125d6b BOOTPROTO=dhcp HWADDR="20:cf:30:e8:57:cf" TYPE=Ethernet NAME="Boot Disk" I've manually added to make it network boot again. NM_CONTROLLED=no
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
There is clearly a bug in the f17 updates from the f17 that will render the NetworkManager to clash with rootfs over iscsi. That been said, It's working fine with f19, so closing