Description of problem:
I have this reproduced with systemd+anaconda, hard to tell if it manifests elsewhere. Also showed this to jklimes who confirmed this looks weird.
Steps to Reproduce:
1. let networkmanger activate a network device with
2. comment out BOOTPROTO, and set ONBOOT and NM_CONTROLLED to "no"
3. observe via 'ip addr' the device went down
4. change the file back, that is uncomment BOOTPROTO and give yes to ONBOOT and NM_CONTROLLED. save the file once
there's a log message in syslog saying 'ifcfg-rh: parsing ...', but the device is not brought up.
the device is configured via dhcp
It is sufficient at this stage to open the file in vim and just save it again with ':w' to trigger NM to bring the device up.
Created attachment 493471 [details]
This is a regression in NM 0.9. I've tested that on F14 (NetworkManager-0.8.3.998-2.fc14.x86_64) and there's no such problem.
NetworkManager-0.8.998-4.git20110427.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.8.998-4.git20110427.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
NetworkManager-0.8.998-4.git20110427.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.