Bug #7489
closed
Missing Timezones from clockConfiguration
Added by Janos Mattyasovszky almost 9 years ago.
Updated over 8 years ago.
Description
There are many-many timezones missing from the Clock config technique.
Please have a look at http://www.unicode.org/cldr/charts/latest/supplemental/zone_tzid.html to get a mapping between linux/windows timezones.
It would be also nice to use an additional input box as "custom" additional to the drop-down menu, so this could be set via Node-Property or generic_variable_definition, as this is a one-technique-per-node setting, so having one rule to rule them all is not applicable, when not all your servers are in one timezone (which is not always the case ;-))
Related to #7488
- Description updated (diff)
- Related to Bug #7488: clockConfiguration sets RTC to localtime added
- Related to Bug #7501: Technique "Clock settings" uses Europe/Paris as China's timezone (technique version 3.0) added
Closing in favour of #7598.
- Is duplicate of User story #7598: Add features to Time settings (RTC to UTC/Localtime; all timezones) added
- Status changed from New to Rejected
- Status changed from Rejected to New
- Assignee set to Jonathan CLARKE
- Target version set to 2.11.19
- Found in version(s) old 2.11.17 added
- Found in version(s) old deleted (
3.0.9)
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/860
- Status changed from New to Pending release
- % Done changed from 0 to 100
- Related to Bug #8009: Fix invalid metadata.xml statement in clockSettings 3.1 added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.
Also available in: Atom
PDF