Created attachment 354523 [details] anaconda.log Description of problem: When booting the installer using rawhide pxeboot images, loader is unable to acquire an IP address. Version-Release number of selected component (if applicable): * http://kojipkgs.fedoraproject.org/mash/rawhide-20090721/development How reproducible: * tested on baremetal and KVM guest Steps to Reproduce: 1. Update grub.conf to use rawhide vmlinuz+initrd.img 2. Reboot 3. Attempt to perform a network-based URL install 4. Select correct NIC with cable attached Actual results: ┌────────┤ Network Error ├─────────┐ │ │ │ There was an error configuring │ │ your network interface. │ │ │ │ ┌───────┐ │ │ │ Retry │ │ │ └───────┘ │ │ │ │ │ └──────────────────────────────────┘ Expected results: * Stage#2 anaconda Additional info: * Extracted dmesg, anaconda.log and syslog from /tmp using busybox (see attached files)
Created attachment 354525 [details] dmesg.log
Created attachment 354526 [details] syslog
*** Bug 513021 has been marked as a duplicate of this bug. ***
It appears that I can work past this issue if I: 1) boot with an image that includes /sbin/busybox 2) Manually start nm-system-settings: `nm-system-settings --plugins ifcfg-rh`
The problem appears to be: F11: drwxr-xr-x 2 root root 0 Jun 2 18:17 lib64/dbus-1 -rwsr-x--- 1 root dbus 44752 Mar 16 13:44 lib64/dbus-1/dbus-daemon-launch-helper Rawhide: drwxr-xr-x 2 root root 0 Jul 21 10:17 lib64/dbus-1 -rwsr-x--- 1 root pulse-ac 45976 Jul 16 16:05 lib64/dbus-1/dbus-daemon-launch-helper
The group ownership on this file seems to have changed after the 20090714 compose. Sadly, there was a stretch of days without images after that so it's hard to tell what might have gone wrong. Jesse - any ideas?
Lots of investigation later, it seems that dbus, while reserving the right to use group ID of 81, doesn't actually /use/ 81 when it is creating the user/group. It instead lets the system pick a number for it. This means it relies upon rpm ordering to get a number each time, and in the case where we're building rawhide, that order can change badly. Anyway the solution seems to be hardcode the group ID of dbus and make sure it uses that. This way the gid will always be the same everywhere and rpm ordering can't effect it. Re-assigning to dbus so that the build can be done hardcoding it.
still broken in 12.4. lots of ** (process: 108): warning** couldn't connect to system bus errors on startup and then when trying to get a network connection get there was an error dialogue box saying couldn't configure network. In tty 4 a msg: get connection (2084): could not connect to system bus.
The attempted fix yesterday wasn't quite correct, I did another build this morning that should work.
should this be in MODIFIED state, then? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
correcting comment 8. still broken in 12.5.
Also tested and confirmed with rawhide-20090724 (anaconda-12.5-1.fc12 and dbus-1.2.16-3.fc12)