Project

General

Profile

Actions
Copy link

Bug #14832

closed

Postgresql is not started properly at postinstall on sles12

Added by Benoît PECCATTE almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Packaging
Target version:
5.0.10
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

This is beacause sles12 doesn't use stsyemd for postgresql

Related issues 1 (0 open — 1 closed)

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

Updated by Benoît PECCATTE almost 5 years ago

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

Updated by Benoît PECCATTE almost 5 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
Copy link
 #3

Updated by Rudder Quality Assistant almost 5 years ago

  • Assignee changed from Alexis Mousset to Benoît PECCATTE
Actions
Copy link
 #4

Updated by Benoît PECCATTE almost 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 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
Copy link
 #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link
 #7

Updated by Félix DALLIDET over 4 years ago

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

Also available in: Atom PDF