Hide Forgot
Created attachment 1247271 [details] screen shot Description of problem: For some reason when we try to save replication setting on the global its trying to connect with peer mode, and its ignoring md5 mode. [----] E, [2017-02-01T13:29:25.976095 #22839:13c6e40] ERROR -- : MIQ(ops_controller-pglogical_save_subscriptions): Error during replication configuration save: Failed to save subscription to 172.27.18.120: ERROR: could not connect to the postgresql server: FATAL: Peer authentication failed for user "root" Remote Setting: ### [root@cloud-azr-bd01 etice]# cat /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf # TYPE DATABASE USER ADDRESS METHOD local all all peer map=usermap host all all all md5 #hostssl all all all md5 host replication all all md5 ### Version-Release number of selected component (if applicable): Customer updated from 4.0 to 4.1, and 4.2 When I setup replication 4.2 appliances everything look good How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This feels like a step was missed in the migration process. In the upgrade document [1] there is a step to add a line to pg_ident.conf Add the following line in the /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_ident.conf file: usermap postgres root Can you ensure that this line was added to all postgres servers (remote and global)? We're working to reproduce this locally. [1] https://access.redhat.com/documentation/en/red-hat-cloudforms/4.2/single/migrating-to-red-hat-cloudforms-42/
I was able to recreate the error with Nick by removing the line mentioned above from the pg_ident.conf file, restarting PG and EVM. Adding the line back to the file file, restarting PG and EVM allow the replication subscription to be created successfully.
Gregg, The customer added the below line to the global and everything looks good now. usermap postgres root
As this was a missed upgrade step. I'm going to close this as NOTABUG.