Bug #7501
closed
Technique "Clock settings" uses Europe/Paris as China's timezone (technique version 3.0)
Added by Janos Mattyasovszky almost 9 years ago.
Updated over 7 years ago.
Description
Beijing is timezoned to Paris again with technique version 3.0:
See Bug #6450.
rudder-techniques-3.1.4.release-1.SLES.11
server:/var/rudder/configuration-repository/techniques/systemSettings/misc/clockConfiguration # grep -i beijing:: -A4 */*.st
1.0/clockConfiguration.st: clock_set_beijing::
1.0/clockConfiguration.st-
1.0/clockConfiguration.st- "linux_timezone" string => "Asia/Shanghai";
1.0/clockConfiguration.st- "windows_timezone" string => "China Standard Time";
1.0/clockConfiguration.st-
--
2.0/clockConfiguration.st: clock_set_beijing::
2.0/clockConfiguration.st-
2.0/clockConfiguration.st- "linux_timezone" string => "Asia/Shanghai";
2.0/clockConfiguration.st- "windows_timezone" string => "China Standard Time";
2.0/clockConfiguration.st-
--
3.0/clockConfiguration.st: clock_set_beijing::
3.0/clockConfiguration.st-
3.0/clockConfiguration.st- "linux_timezone" string => "Europe/Paris";
3.0/clockConfiguration.st- "windows_timezone" string => "China Standard Time";
3.0/clockConfiguration.st-
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/802
- Description updated (diff)
- Status changed from New to In progress
- Assignee set to Janos Mattyasovszky
- Target version set to 2.11.17
As explained in the PR this needs retargeting to 2.11.
By the way, if you use rudder-dev, this is all automatic :-)
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/802 to https://github.com/Normation/rudder-techniques/pull/803
- Assignee changed from Janos Mattyasovszky to Jonathan CLARKE
Regarding rudder-dev: try to use it behind a firewall and necessary proxy. It's full with curl and git commands, that expect to have direct Internet access...
- Related to Bug #7489: Missing Timezones from clockConfiguration added
Janos Mattyasovszky wrote:
Regarding rudder-dev: try to use it behind a firewall and necessary proxy. It's full with curl and git commands, that expect to have direct Internet access...
Aha! Good to know. Well, that's a bad thing obviously, but I didn't know that was an adoption barrier. I have opened ticket #7507 to fix this. I suggest that you "watch" it so that you could use it in the future :)
- Status changed from In progress to Pending technical review
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/803 to https://github.com/Normation/rudder-techniques/pull/808
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.17, 3.0.12 and 3.1.5 which were released today.
- Found in version (s) 3.1.2 added
- Found in version(s) old deleted (
3.1.2)
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by