Actions
Bug #16470
closed
Postgresql service name is not detected properly on SLES 12
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
This is beacause sles12 doesn't use stsyemd for postgresql
Updated by Félix DALLIDET almost 5 years ago
- Related to Bug #14832: Postgresql is not started properly at postinstall on sles12 added
Updated by Félix DALLIDET almost 5 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1570
Updated by Félix DALLIDET almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|4f9947f6cab7bdc074e5813f20a44c02f90426de.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset almost 5 years ago
- Subject changed from Postgresql service name is not detected properly on sles12 to Postgresql service name is not detected properly on SLES 12
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.2 which was released today.
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #17145: Rudder 6 check postgresql process failes added
Actions