geolocation regression in final TC1 from beta RC5

[Thomas Gilliard]

On 11/16/2013 11:33 AM, Chris Murphy wrote:
> On Nov 16, 2013, at 10:20 AM, Chris Murphy <lists at colorremedies.com> wrote:
>
>> What component to file anaconda geolocation bugs?
>>
>> In qemu/kvm, 100% of the time DVD beta RC5 anaconda sets American/Denver timezone, which is correct. And 100% of the time DVD final TC1 anaconda sets Pacific/Honolulu timezone, which is incorrect. I haven't tested desktop live.
I see this often in live boot using VirtalBox as I am on wireless and 
WEP network is not available at boot.
netinstall has wireless setup before anaconda main hub so it does have 
networking available for geolocation.
-I think

Tom Gilliard
> I filed a bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1031319
>
>
> These are the same versions of anaconda, 20.25.6-1. There seems to be a delay or hiccup with Network Manager that may be related to why anaconda fails to do a geoip lookup.
>
> Final TC1
> [liveuser at localhost tmp]$ cat anaconda.log | grep -i geo
> 13:49:00,866 INFO anaconda: Running Thread: AnaGeolocationRefreshThread (140083109820160)
> 13:49:00,895 INFO anaconda: Starting geolocation lookup
> 13:49:00,895 INFO anaconda: Geolocation provider: Fedora GeoIP
> 13:49:00,977 DEBUG anaconda: Geoloc: URLError for Fedora GeoIP API lookup:
> 13:49:00,978 INFO anaconda: Geolocation lookup finished in 0.1 seconds
> 13:49:00,980 INFO anaconda: no results from geolocation
> 13:49:00,981 INFO anaconda: Thread Done: AnaGeolocationRefreshThread (140083109820160)
>
> Beta RC5
> 14:02:10,954 INFO anaconda: Running Thread: AnaGeolocationRefreshThread (140432201737984)
> 14:02:11,039 INFO anaconda: Starting geolocation lookup
> 14:02:11,039 INFO anaconda: Geolocation provider: Fedora GeoIP
> 14:02:11,466 INFO anaconda: Geolocation lookup finished in 0.4 seconds
> 14:02:11,477 INFO anaconda: got results from geolocation
> 14:02:11,477 INFO anaconda: Thread Done: AnaGeolocationRefreshThread (140432201737984)
>
>
>
> Chris Murphy