Bug 1389029 - [RFE] Ability to re-configure Database Replication in appliance_console
Summary: [RFE] Ability to re-configure Database Replication in appliance_console
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Jaroslav Henner
URL:
Whiteboard: black:replication
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 17:04 UTC by Jared Deubel
Modified: 2019-07-08 12:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-08 12:05:55 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Jared Deubel 2016-10-26 17:04:33 UTC
Description of problem:
Currently we are not able to re-configure Database Replication on Primary and Secondary.

Since it has been already configured it won't let you make changes if you accidental configured it wrong or have hardware changes. 

We should have a way (through console or documentation) on how to re-configure and not blow up in the appliance_console (exit cleanly).

ERROR message snippet:
==========================================
Replication Server Configuration

        Cluster Node Number:        1
        Cluster Database Name:      vmdb_production
        Cluster Database User:      root
        Cluster Database Password:  "********"
        Cluster Primary Host:       10.10.181.47
Apply this Replication Server Configuration? (Y/N): y
Configuring Primary Replication Server...
[2016-10-26 12:58:27] [ERROR] there is a master already in cluster
miq_region_99_cluster
Failed to configure replication server
/opt/rh/cfme-gemset/gems/awesome_spawn-1.4.1/lib/awesome_spawn.rb:105:in `run!': repmgr master register 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_primary.rb:43:in `initialize_primary_server'
	from /var/www/miq/vmdb/gems/pending/appliance_console/database_replication_primary.rb:39: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):
5.7.0.1 Beta1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 German Pulido 2017-05-22 23:41:33 UTC
What is the current workaround for reconfiguring the replication if needed, while this RFE is implemented?


Note You need to log in before you can comment on or make changes to this bug.