Project

General

Profile

Actions
Copy link

Bug #6737

closed

Make all techniques compatible with systemd changes

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

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Check compatibility of Rudder 3.0 techniques with systemd.

  • process name may have changed
  • /etc/init.d/ does not work anymore (except for rudder services, at least for now)

Subtasks 9 (0 open — 9 closed)

Bug #6736: The cron_bin in system's promises.st is not compatible with RHEL7ReleasedMatthieu CERDA2015-06-10Actions
Bug #6735: cronConfiguration is not compatible with RHEL 7 and SLES 12ReleasedMatthieu CERDA2015-06-17Actions
Bug #6766: cronConfiguration is broken because of duplicate definition of cron_binReleasedMatthieu CERDA2015-06-17Actions
Bug #6566: promises.cf's "bundle agent check_cron_daemon" is not systemd awareReleasedMatthieu CERDA2015-05-06Actions
Bug #6740: rsyslogConf in initial-promises still uses /etc/init.d for service managementReleasedMatthieu CERDA2015-06-11Actions
Bug #6742: postgres-check still uses /etc/init.d/ for service managementRejected2015-06-11Actions
Bug #6743: generic_process_check_process in init-check still uses /etc/init.dReleasedMatthieu CERDA2015-06-11Actions
Bug #6783: generic_process_check_bootstart in initial promises is not compatible with systemdRejected2015-06-23Actions
Bug #9678: clockConfiguration does not work properly on SLES12/systemdRejectedActions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #6772: clockConfiguration is not compatible with systemd-based systemsReleasedBenoît PECCATTEActions
Actions
Copy link

Also available in: Atom PDF