Description of problem: Is set automatically on launch with Fedora 22 workstation live, but is not automatically set in Fedora-Live-Workstation-x86_64-rawhide-20150704.iso Version-Release number of selected component (if applicable): anaconda 23.13-1 How reproducible: Always Steps to Reproduce: 1. Boot media, launch installer, pick a language 2. 3. Actual results: Timezone set to Americas/New York Expected results: Timezeone set to Americas/Denver Additional info: logs suggest network and geoip retrieval is working the same on F22 and F23, so I'm not sure what the problem is.
Created attachment 1049538 [details] f22 anaconda.log
Created attachment 1049539 [details] f22 program.log
Created attachment 1049540 [details] f22 ifcfg.log
Created attachment 1049541 [details] f23 anaconda.log
Created attachment 1049542 [details] f23 program.log
Created attachment 1049543 [details] f23 ifcfg.log
I am in same time zone as Toronto Canada (New York) -- gmt-5 My presentation is showning me one timezone to the west (gmt-6) (Winnipeg / Manitoba) Fedora-Workstation-netinst-x86_64-23_Alpha_TC2.iso There may be an explanation if my ISP is hosting me from 1500 miles away at Winnipeg instead of Montreal, Quebec. The hosting company is Bell Canada. This is a low priority error as I reset the timezone and continue with the Anaconda installation.
What is the time_zone field set to if you just go to https://geoip.fedoraproject.org/city ? I suspect it's "null" for both of you. If geoloc returns a territory but not a timezone, anaconda will just pick the first thing that comes out langtable.list_timezones, which for the US is America/New_York, and for CA is America/Winnipeg. Obviously this works better for less longitudinally diverse territories, but there isn't a whole lot else we can do. langtable has a weight for each zone, and in the case of Canada America/Winnipeg is tied for the highest, along with Vancouver, Toronto, Saint_Johns, Regina, Hallifax, Edmonton and Creston. I suppose you could argue that some of those zones are much more populous than others, but that's something for langtable. In the case of the US New_York is the highest weighted zone. I don't know offhand the population difference between the east and west coasts but given how wide the eastern time zone is that seems probably right. Short version: I suspect the Fedora geoloc service is returning no data and anaconda is just doing the most with what it got.
I just booted Fedora-Live-KDE-x86_64-23-20150813.iso and it still wrongly sets Time & Date to America/New York. In Konqueror in this live environment, for https://geoip.fedoraproject.org/city I get: {"city": "Steamboat Springs", "region_name": "Colorado", "ip": "69.7.127.113", "region": "CO", "area_code": 970, "time_zone": "America/Denver", "longitude": -106.92720031738281, "metro_code": 751, "country_code3": "USA", "latitude": 40.62649917602539, "postal_code": "80487", "dma_code": 751, "country_code": "US", "country_name": "United States"} Like I mentioned in the description, Time & Date is set properly with Fedora 22's install media.
{"city": "Montr\u00e9al", "region_name": "Quebec", "ip": "70.27.241.28", "region": "QC", "area_code": 0, "time_zone": "America/Montreal", "longitude": -73.67040252685547, "metro_code": 0, "country_code3": "CAN", "latitude": 45.47800064086914, "postal_code": "H4W", "dma_code": 0, "country_code": "CA", "country_name": "Canada"} Montréal with accent on the e. By the way, at one time Montreal was included (Fedora 20/21), but Quebec was removed sometime later and we were left with two choices. Toronto, or New York Fedora 23 is currently experiencing same problem
American_Montreal is not in the anaconda list of time-zones.
I don't know if it's related but Anaconda's Region pop-up says "Americas" whereas the geoip data returns America/Denver – no s.
(In reply to Leslie Satenstein from comment #11) > American_Montreal is not in the anaconda list of time-zones. Correct. IANA removed America/Montreal from tzdata in the 2013e release, because it turned out that Montréal and Toronto have used the same time since at least 1970 (IANA's criteria whether to define a time zone), so Montréal and Toronto being separate in the first place was a mistake. Removing it has obviously caused some confusion. The Fedora geoip service should be returning America/Toronto, and I'll file a ticket with Fedora infrastructure about that. (In reply to Chris Murphy from comment #12) > I don't know if it's related but Anaconda's Region pop-up says "Americas" > whereas the geoip data returns America/Denver – no s. I think that's something langtable to make it more clear that the America/ tzdata category is for all of North and South America and not just the US. America/Denver is what is in tzdata and is what should be used by geoip and anaconda at that stage. And is_valid_timezone is returning True for America/Denver, so still no clue why your case isn't working.
(In reply to David Shea from comment #13) > I'll file a ticket with Fedora infrastructure about that. https://fedorahosted.org/fedora-infrastructure/ticket/4859
The rest of the problem was 2->3 string types, turns out.