Bug #6546
closed
rudder-reports package should use the correct PostgreSQL service
Added by Matthieu CERDA over 9 years ago.
Updated over 9 years ago.
Category:
System integration
Description
We currently assume (naively ?) that the right PostgreSQL service to run is "postgresql".
We should certainly be more intelligent and try to guess the right one :)
- Target version changed from 2.10.14 to 2.11.11
Targetting 2.11 as this happens especially on distributed setups.
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Benoît PECCATTE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/647
- Status changed from Pending technical review to Pending release
- Subject changed from The rudder-reports package should be able to use the right PostgreSQL service to rudder-reports package should use the correct PostgreSQL service
- Related to Bug #6699: Rudder-reports does not find correct postgresql service when using systemctl added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.11 and 3.0.5 which were released today.
- Related to Bug #6403: Postgresql misconfigured when not the default distrib package (ex: Centos 6 with Postgresql 9.3 from pgfoundry.org) added
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by 
Updated by