Description of problem:
Replication Server Configuration
Cluster Node Number: 2
Cluster Database Name: vmdb_production
Cluster Database User: root
Cluster Database Password: "********"
Cluster Primary Host: 172.26.2.120
Standby Host: 172.26.2.227
Automatic Failover: enabled
Apply this Replication Server Configuration? (Y/N): Y
Configuring Replication Standby Server...
[2017-02-07 12:15:42] [NOTICE] destination directory
[2017-02-07 12:15:42] [ERROR] parameter 'max_replication_slots' must be set to
at least 1 to enable replication slots
[2017-02-07 12:15:42] [HINT] 'max_replication_slots' should be set to at least
the number of expected standbys
Failed to configure replication server
/opt/rh/cfme-gemset/gems/awesome_spawn-1.4.1/lib/awesome_spawn.rb:105:in `run!': repmgr exit code: 1 (AwesomeSpawn::CommandResultError)
from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication.rb:101:in `block in run_repmgr_command'
from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication.rb:98:in `fork'
from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication.rb:98:in `run_repmgr_command'
from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication_standby.rb:86:in `clone_standby_server'
from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication_standby.rb:62:in `activate'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:488:in `block in <module:ApplianceConsole>'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:109:in `loop'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:109:in `<module:ApplianceConsole>'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:95:in `<main>'
Database Replication not configured
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is probably just a documentation issue.
There were some changes recently to how we documented editing postgresql.conf between versions.
Can you make sure that the values in  have been properly set on all postgres servers?
I'm going to close this as NOTABUG. We were not able to reproduce the issue and there has been no activity for a week after a fix was suggested.