Project

General

Profile

Actions

Bug #14832

closed

Postgresql is not started properly at postinstall on sles12

Added by Benoît PECCATTE about 2 years ago. Updated almost 2 years 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
Actions #1

Updated by Benoît PECCATTE about 2 years ago

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

Updated by Benoît PECCATTE about 2 years 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
Actions #3

Updated by Rudder Quality Assistant about 2 years ago

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

Updated by Benoît PECCATTE about 2 years ago

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

Updated by Vincent MEMBRÉ almost 2 years ago

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

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

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

Actions #7

Updated by Félix DALLIDET over 1 year ago

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

Also available in: Atom PDF