Project

General

Profile

Bug #14832

Postgresql is not started properly at postinstall on sles12

Added by Benoît PECCATTE over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

This is beacause sles12 doesn't use stsyemd for postgresql


Related issues

Related to Rudder - Bug #16470: Postgresql service name is not detected properly on SLES 12 ReleasedBenoît PECCATTEActions
#1

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
#2

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1895
#3

Updated by Rudder Quality Assistant over 1 year ago

  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
#4

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from Pending technical review to Pending release
#5

Updated by Vincent MEMBRÉ over 1 year ago

  • Subject changed from postgresql is not started properly at postinstall on sles12 to Postgresql is not started properly at postinstall on sles12
#6

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.10 which was released today.

#7

Updated by Félix DALLIDET 9 months ago

  • Related to Bug #16470: Postgresql service name is not detected properly on SLES 12 added

Also available in: Atom PDF