Project

General

Profile

Actions

Bug #6772

closed

clockConfiguration is not compatible with systemd-based systems

Added by Alexis Mousset almost 9 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Medium
Priority:
0
Name check:
Fix check:
Regression:

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.


Related issues 7 (1 open6 closed)

Related to Rudder - Bug #6737: Make all techniques compatible with systemd changesRejected2015-05-06Actions
Related to Rudder - Bug #14369: timezone technique does not support systemdNewNicolas CHARLESActions
Has duplicate Rudder - Bug #8457: Timezone correction on RHEL-7Rejected2016-06-03Actions
Has duplicate Rudder - Bug #9086: Generic setup time not OK on Centos7RejectedActions
Has duplicate Rudder - Bug #9696: Time settings technique (still) cannot set timezone on Red HatRejectedAlexis MoussetActions
Has duplicate Rudder - Bug #8199: Use ncf in clockConfiguration to make it compatible with recent OSesRejectedAlexis MoussetActions
Has duplicate Rudder - Bug #9678: clockConfiguration does not work properly on SLES12/systemdRejectedActions
Actions

Also available in: Atom PDF