Version-Release number of selected component: anaconda-20.25.5-1 The following was filed automatically by anaconda: anaconda 20.25.5-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/ntplib.py", line 279, in request s.sendto(query_packet.to_data(), sockaddr) File "/usr/lib64/python2.7/site-packages/pyanaconda/ntp.py", line 61, in ntp_server_working client.request(server) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/datetime_spoke.py", line 189, in _set_server_ok_nok server_working = ntp.ntp_server_working(self._serversStore[itr][0]) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run threading.Thread.run(self, *args, **kwargs) error: [Errno 101] Network is unreachable Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz noipv4 ip=[2001:838:3ab:1::70]::[2001:838:3ab:1::1]:64:cfl.digifarma.nl::off nameserver=2001:838:3ab:1::1 inst.stage2=hd:UUID=3cd4da1d-ffdf-4320-afb0-b375dc0d0fb8 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.6-300.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Beta
Created attachment 818747 [details] File: anaconda-tb
Created attachment 818748 [details] File: anaconda.log
Created attachment 818749 [details] File: environ
Created attachment 818750 [details] File: lsblk_output
Created attachment 818751 [details] File: nmcli_dev_list
Created attachment 818752 [details] File: os_info
Created attachment 818753 [details] File: program.log
Created attachment 818754 [details] File: storage.log
Created attachment 818755 [details] File: syslog
Created attachment 818756 [details] File: ifcfg.log
Created attachment 818757 [details] File: packaging.log
This error happens when NIC is only configured with IPv6 and without IPv4
Looks like the geoip stuff fails in this case, but it shouldn't bring down the installer with it...
*** Bug 1017167 has been marked as a duplicate of this bug. ***
possibly worth an FE.
Note that the fedora infrastructure provided geoip service is deliberately ipv4 only. Maxmind does not provide a free ipv6 geoip-lite-city. So, likely in an ipv6 only env, anaconda should just skip the geoip check (since it can't reach it via ipv6 only and even if it could, it wouldn't have any ipv6 data).
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted an AcceptedFreezeException. There is some sentiment that it could be promoted to a blocker if 'geoloc=0' does not work around the issue, we should ask the reporter to check. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/
Crash after suggestion made in bug 1026079 comment #17. I used geoloc=0. With a kickstart I see the crash report screen, but after a little hassitation anaconda progresses. Without a kickstart thios crash comes up. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz ip=[2001:838:3ab:1::70]::[2001:838:3ab:1::1]:64:cfl.digifarma.nl::off geoloc=0 nameserver=2001:838:3ab:1::1 inst.stage2=hd:UUID=39a4e5f4-19ec-4bb0-8e24-c748085ae986 hashmarkername: anaconda kernel: 3.11.10-300.fc20.x86_64 package: anaconda-20.25.14-1 product: Fedora reason: error: [Errno 101] Network is unreachable release: Cannot get release name. version: 20-TC5
(In reply to A.J. Werkman from comment #18) > Crash after suggestion made in bug 1026079 comment #17. I used geoloc=0. > With a kickstart I see the crash report screen, but after a little > hassitation anaconda progresses. Without a kickstart thios crash comes up. > > cmdline: /usr/bin/python /sbin/anaconda > cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz > ip=[2001:838:3ab:1::70]::[2001:838:3ab:1::1]:64:cfl.digifarma.nl::off > geoloc=0 nameserver=2001:838:3ab:1::1 > inst.stage2=hd:UUID=39a4e5f4-19ec-4bb0-8e24-c748085ae986 > hashmarkername: anaconda > kernel: 3.11.10-300.fc20.x86_64 > package: anaconda-20.25.14-1 > product: Fedora > reason: error: [Errno 101] Network is unreachable > release: Cannot get release name. > version: 20-TC5 The exception is actually raised when querying NTP servers and is not related to geolocation at all. That's why even if you disable geolocation, it still crashes.
The orig report was about geoloc... the later test was to see if geoloc=0 worked around the issue, which it did but hit the ntp thing. So, I think it would still be desireable to fix the geoloc issue on a ipv6 only network? Or are we assuming we want to ask all ipv6 only users to pass geoloc=0?
(In reply to Kevin Fenzi from comment #20) > The orig report was about geoloc... the later test was to see if geoloc=0 > worked around the issue, which it did but hit the ntp thing. > > So, I think it would still be desireable to fix the geoloc issue on a ipv6 > only network? Or are we assuming we want to ask all ipv6 only users to pass > geoloc=0? Yes, it was reported against geoloc, but incorrectly. Quoting the traceback from first comment: <snip> Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/ntplib.py", line 279, in request s.sendto(query_packet.to_data(), sockaddr) File "/usr/lib64/python2.7/site-packages/pyanaconda/ntp.py", line 61, in ntp_server_working </snip> As you can see, the exception is being raised during a NTP server query. BTW, I've also checked how geolocation behaves if the network interface has only a IPv6 address it works fine - just logs an error (which is correct according to comment 16), no crash or any other unexpected behavior.
Ah, quite right. Sorry for the digression and thanks for the prompt fix. ;)
yeah, looking back at the original backtrace, there is a 'Network is unreachable' error while it's doing geoloc, but the crash handler isn't invoked till 8 seconds later, right when NTP happens. So the same error is fatal to NTP but not geoloc...
anaconda-20.25.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.15-1.fc20
Package anaconda-20.25.15-1.fc20, python-blivet-0.23.9-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.25.15-1.fc20 python-blivet-0.23.9-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23257/python-blivet-0.23.9-1.fc20,anaconda-20.25.15-1.fc20 then log in and leave karma (feedback).
anaconda-20.25.15-1.fc20, python-blivet-0.23.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1043064 has been marked as a duplicate of this bug. ***