Project

General

Profile

Actions

Bug #10488

closed

Do not use systemd to manage legacy init scripts

Added by Alexis Mousset about 7 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

The issue is that systemd does not have proper inital track of the state of traditionnal init services. It means that mixing service/etc/init.d calls with systemctl cause trouble.

For example, if systemd thinks a service is not running (for example if it has been started usint the init script directly, wich is the case on CentOS7 using the service command), when asking for a restart, it will not stop the service but only try to start it, which will break...

It may break running systems when updating ncf, so we should use the init script when it is there.

Actions #1

Updated by Alexis Mousset about 7 years ago

  • Status changed from New to In progress
Actions #2

Updated by Alexis Mousset about 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/ncf/pull/553
Actions #3

Updated by Alexis Mousset about 7 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:3966fbc4c77cc5aa82325a8faf520ff1e9aa7599.

Actions #4

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released
  • Priority set to 0
Actions #5

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from master to ncf-1.2
Actions #6

Updated by Alexis Mousset almost 2 years ago

  • Project changed from 41 to Rudder
  • Category changed from Generic methods - Service Management to Generic methods
Actions

Also available in: Atom PDF