Actions
tickets #54503
closedmirrordb1: /etc/postgresql/pg_hba.conf from salt breaks postgresql
Start date:
2019-07-21
Due date:
% Done:
0%
Estimated time:
Description
I'll be lazy and paste from IRC ;-)
[19:23:53] <cboltz> kbabioch_: do you have some time to get the postgresql config of reality and salt in sync, or should I open a ticket?
[19:24:17] <kbabioch_> ticket is appreciated ... jsut to not forget about it ;-)
[19:24:26] <cboltz> ok
[19:24:27] <kbabioch_> do you know who has touched it the last?
[19:24:35] <kbabioch_> or which postgres config are we talking about?
[19:24:54] <cboltz> /etc/postgresql/pg_hba.conf on mirrordb1
[19:27:10] <cboltz> I made the mistake of running highstate some days ago (with the intention to deploy the package whitelist for the monitoring)
[19:27:25] <cboltz> as a side effect, the salt-deployed config broke - at least a monitoring check complained
[19:28:22] <cboltz> I partially reverted the changes to pg_hba.conf - the file in salt looks like someone did cleanup / comment out too much
[19:29:21] <cboltz> (the salt-deployed file and the diff to the previous pg_hba.conf are in /etc/postgresql/ on mirrordb1 as pg_hba.conf--*)
Updated by lrupp about 4 years ago
- Assignee changed from kbabioch to cboltz
JFYI: I synced pg_hba.conf and postgresql.conf on mirrordb1 and mirrordb2. Both should be deployable via salt now.
Updated by cboltz about 4 years ago
- Status changed from New to Closed
Thanks, I commited the unified files to salt: https://gitlab.infra.opensuse.org/infra/salt/-/merge_requests/397
Please do future changes directly in salt, and then do a highstate to deploy them.
Actions