Bug #11551
closed
Invalid Timezone: Europe/Busingen in chrome after upgrading to foreman 1.9.0
Description
Hi,
I have just upgraded to latest foreman 1.9.0 and when I try to login using chrome browser I get this error:
Warning! Invalid Timezone: Europe/Busingen
The weird thing is that I can login without issues with firefox. I have tried to clean cookies and cache in chome. Also tried to use incognito mode. Also tried to login with firefox and in the user settings for this user account switch from "Browser Timezone" to select an specific one. None of this worked. I can login with firefox but not with chrome.
Here is the trace log:
https://gist.github.com/anonymous/07a873294e82a51ab119
Updated by Pablo Escobar over 8 years ago
by the way the timezone in my desktop machine is Europe/Zurich. I could not find
Updated by Dominic Cleal over 8 years ago
- Category set to Web Interface
Which OS are you on precisely?
Updated by Pablo Escobar over 8 years ago
Foreman is running on Centos 6.6
My desktop is Linux Mint 17.2 (Based on Ubuntu 14.04)
Chrome is Version 44.0.2403.155 (64-bit)
Updated by Dominic Cleal over 8 years ago
Please try running "yum upgrade tzdata" on your Foreman server, you need at least tzdata-2013b-1.el6 I think to get that timezone.
Not sure precisely why you're needing it, but I guess Chrome is sending/changing it.
Updated by Pablo Escobar over 8 years ago
I tried "yum update tzdata" and the system updated from tzdata-2014j-1.el6.noarch to tzdata-2015f-1.el6.noarch. After that I tried "service httpd restart" and tried to login with chrome in an incognito window. Still the same error appears. Maybe is there any other service I should restart?
Updated by Dominic Cleal over 8 years ago
Oh sorry, we're still using a version of tzinfo that doesn't use the system's tzdata. I don't think there's any fix until we update these dependencies via #3157, apart from hacking around in opt/rh/ruby193/root/usr/share/gems/gems/tzinfo-0.3.33/lib/tzinfo/ to copy Zurich to Busingen or similar.
Updated by Pablo Escobar over 8 years ago
ok, I will keep using firefox until this is fixed.
thanks for the quick reply!
Updated by Anonymous