Bug #9678: clockConfiguration does not work properly on SLES12/systemd - Rudder - Issue Tracker

Actions

Copy link

Bug #9678

closed

Bug #6737: Make all techniques compatible with systemd changes

clockConfiguration does not work properly on SLES12/systemd

Added by Janos Mattyasovszky about 8 years ago. Updated over 7 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Techniques

Target version:

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Hi,

The systemSettings/misc/clockConfiguration/3.1/clockConfiguration.st is not sles12/systemd capable:

Line 125:

    SuSE_11::
      "ntp" 
        package_policy => "add",
        package_method => zypper,
        classes => kept_if_else("ntp_install_kept", "ntp_installed", "cant_install_ntp"),
        comment => "Installing ntp using zypper";

=> This should probably also include the SuSE_12 class.

Line 275:

    !windows.!redhat.(repaired_ntpconf|repaired_localtime|repaired_debiantz|repaired_susetz|ntpd_down)::
      "/etc/init.d/ntp" 
        args => "restart",
        classes => cf2_if_else("ntp_restarted", "cant_restart_ntp"),
        comment => "restarting ntp";

    redhat.(repaired_ntpconf|repaired_localtime|repaired_redhattz|ntpd_down)::
      "/etc/init.d/ntpd" 
        args => "restart",
        classes => cf2_if_else("ntp_restarted", "cant_restart_ntp"),
        comment => "restarting ntp";

This is also not systemd-service aware.

Related issues 1 (0 open — 1 closed)