Bug #6772
closedclockConfiguration is not compatible with systemd-based systems
Description
/etc/sysconfig/clock does not exist anymore.
2015-06-18T11:27:48+0200 error: /default/check_clock_configuration/files/'/etc/sysconfig/clock'[0]: Promised to edit '/etc/sysconfig/clock', but file does not exist
We could use timedatectl instead.
We also need proper package and service management.
CentOS 7 also generally uses chrony as default ntp service.
Updated by Alexis Mousset over 9 years ago
- Subject changed from clockConfiguration non compatble with RHEL7 to clockConfiguration is not compatible with RHEL7
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.0.7 to 3.0.8
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.0.8 to 3.0.9
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.9 to 3.0.10
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.10 to 3.0.11
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.11 to 3.0.12
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.12 to 3.0.13
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.0.13 to 3.0.14
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.0.14 to 3.0.15
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.15 to 3.0.16
Updated by Alexis Mousset over 8 years ago
- Related to Bug #8199: Use ncf in clockConfiguration to make it compatible with recent OSes added
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.16 to 3.0.17
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.17 to 302
Updated by Alexis Mousset over 8 years ago
- Target version changed from 302 to 3.1.12
Updated by Alexis Mousset over 8 years ago
- Has duplicate Bug #8457: Timezone correction on RHEL-7 added
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by Florian Heigl over 8 years ago
Please could you fix this?
RHEL7 beta has ended quite a while ago :-)
The fix is likely easier than the EL6 implementation was:
http://serverfault.com/questions/666979/why-do-i-need-to-use-systemd-to-set-my-timezone-in-rhel7
It is probably best to just adjust the symlink!
Updated by Florian Heigl over 8 years ago
- Translation missing: en.field_tag_list set to Quick and important
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Alexis Mousset about 8 years ago
- Related to Bug #9086: Generic setup time not OK on Centos7 added
Updated by François ARMAND about 8 years ago
- Related to Bug #9696: Time settings technique (still) cannot set timezone on Red Hat added
Updated by François ARMAND about 8 years ago
- Related to Bug #9678: clockConfiguration does not work properly on SLES12/systemd added
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Alexis Mousset almost 8 years ago
- Subject changed from clockConfiguration is not compatible with RHEL7 to clockConfiguration is not compatible with systemd-based systems
Updated by Alexis Mousset almost 8 years ago
- Related to deleted (Bug #9086: Generic setup time not OK on Centos7)
Updated by Alexis Mousset almost 8 years ago
- Has duplicate Bug #9086: Generic setup time not OK on Centos7 added
Updated by Alexis Mousset almost 8 years ago
- Related to deleted (Bug #9696: Time settings technique (still) cannot set timezone on Red Hat)
Updated by Alexis Mousset almost 8 years ago
- Has duplicate Bug #9696: Time settings technique (still) cannot set timezone on Red Hat added
Updated by Alexis Mousset almost 8 years ago
- Related to deleted (Bug #8199: Use ncf in clockConfiguration to make it compatible with recent OSes)
Updated by Alexis Mousset almost 8 years ago
- Has duplicate Bug #8199: Use ncf in clockConfiguration to make it compatible with recent OSes added
Updated by Alexis Mousset almost 8 years ago
- Related to deleted (Bug #9678: clockConfiguration does not work properly on SLES12/systemd)
Updated by Alexis Mousset almost 8 years ago
- Related to Bug #9678: clockConfiguration does not work properly on SLES12/systemd added
Updated by Alexis Mousset almost 8 years ago
- Related to deleted (Bug #9678: clockConfiguration does not work properly on SLES12/systemd)
Updated by Alexis Mousset almost 8 years ago
- Has duplicate Bug #9678: clockConfiguration does not work properly on SLES12/systemd added
Updated by Jonathan CLARKE almost 8 years ago
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by Jonathan CLARKE almost 8 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Benoît PECCATTE over 7 years ago
- Translation missing: en.field_tag_list deleted (
Quick and important)
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Florian Heigl over 7 years ago
Hey!
This bug just gets to celebrate it's second birthday!
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.25 to 387
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 387 to 4.1.10
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Related to Bug #6737: Make all techniques compatible with systemd changes added
Updated by Vincent MEMBRÉ over 6 years ago
- Effort required set to Medium
- Priority changed from 58 to 44
Two solutions here:
Easy way would be to only use ntp, but that would be really strange behavior for a chrony user ( uninstall chrony, install and configure ntp ...)
other way is to rewrite completely the technique to detect correctly which clock management tool is used, and configure it ... but that would be the correct way!
setting effort to medium
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
- Priority changed from 44 to 45
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 45 to 46
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by Florian Heigl about 6 years ago
Hi,
could we soon find a way to properly support and RHEL/CentOS with config management using Rudder? O_o
Updated by François ARMAND about 6 years ago
- Translation missing: en.field_tag_list set to Sponsored
- Priority changed from 46 to 74
I increased the priority of that one.
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 74 to 0
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset almost 6 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND almost 6 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Nicolas CHARLES almost 6 years ago
- Related to Bug #14369: timezone technique does not support systemd added
Updated by Nicolas CHARLES almost 6 years ago
- Status changed from New to Rejected
implemented in 14369
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Rejected to New
- Target version changed from 4.1.21 to 6.0.8
Reopening thin #14369 was never merged
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 4 years ago
- Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1613
Updated by Anonymous over 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder-techniques|489b99fc321d876a8ffd5409f9ed5f947dd3afa1.
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.8 to 6.0.7
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.7 and 6.1.1 which were released today.