Created attachment 618752 [details] Archive of /tmp/*log After install completes but before reboot: ctrl-alt-f2 # ping google.com # works # chroot /mnt/sysimage # ping google.com ping: unknown host google.com This worked for all previous Fedora versions, and prevents a kickstart %post section from talking to the network.
Please attach logs as individual text/plain files, not as an archive. It makes it easier to search and examine them.
Also please attach /mnt/sysimage/etc/resolv.conf . You might have network access, just not functional DNS resolution, which may be a side effect of using DHCP for network details.
Jesse, there is no /mnt/sysimage/etc/resolv.conf. I assume the installer resolve.conf doesn't matter, but here it is: # cat resolv.conf # Generated by NetworkManager nameserver 192.168.123.1 Rest of the logs coming shortly
Created attachment 620066 [details] anaconda.log
Created attachment 620067 [details] ifcfg.log
Created attachment 620068 [details] packaging.log
Created attachment 620069 [details] program.log
Created attachment 620070 [details] storage.log
Created attachment 620071 [details] X.log
(In reply to comment #3) > Jesse, there is no /mnt/sysimage/etc/resolv.conf. Well there's your problem :) Could you verify that the network functions from the chroot just without name resolution? Also can you tell us what networking configuration you used? I presume it was boot time options?
Yep, I can ping public IP addresses from the chroot. Networking is only configured with a kickstart which has: network --bootproto=dhcp --onboot=on Nothing was configured interactively. And just to clarify, after booting into the newly installed OS, it has no problem resolving host names.
(In reply to comment #10) > (In reply to comment #3) > > Jesse, there is no /mnt/sysimage/etc/resolv.conf. >. Copying networking configuration to installation root was fixed in master but didn't went in F18 Alpha (bug 853584). So if the cause is actually the missing file, which seems to be so, this should be fixed post F18 Alpha. (In reply to comment #11) > Nothing was configured interactively. And just to clarify, after booting > into the newly installed OS, it has no problem resolving host names. Here the resolv.conf is generated by NetworkManager.
You should re-test with the nightly boot.iso to see if the fix works for you.
Let's just assume this is fixed and I'll reopen if I'm still hitting it. Jesse, where are the nightly isos? I see http://alt.fedoraproject.org/pub/alt/nightly-composes/ but not sure if that's what you mean. Any nightly tree I can pull from and get a pxe boot image?
(In reply to comment #14) > Let's just assume this is fixed and I'll reopen if I'm still hitting it. > > Jesse, where are the nightly isos? I see > http://alt.fedoraproject.org/pub/alt/nightly-composes/ but not sure if > that's what you mean. Any nightly tree I can pull from and get a pxe boot > image? http://download.fedoraproject.org/pub/fedora/linux/development/18/<arch>/os/images/