Document URL: https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/high_availability_guide/

Section Number and Name: n/a

Describe the issue: the document does not include the steps to rename appliances, especially the database appliances

Suggestions for improvement: 

the following steps were shared with the customer and he decided to close the case :

follow the steps of https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/high_availability_guide/database_failover#failover_monitor. Basically what you'll have to do to rename your appliances is 

 0 - make sure which is the active database and which is the standby
 1 - stop all monitor on all the non-db appliances in appliance_console
 2 - reset the standby by deleting the database
 3 - stop all evmserverd on the non-db appliances
 4 - do the renaming of the db appliance & restart the appliance 
 5 - on all appliances change the database to the right hostname in vmdb/config/database.yml
 6 - restart the appliances

note : if you use a non-dedicated database appliances also stop evmserverd there before renaming it and reconfigure the database.yml before restarting.

at that point you should have all appliances able to connect to the db. after that you will have to set up again HA from https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/high_availability_guide/installation#configuring_primary_db (part 2.3).

Additional information: 

I haven't had tried to create a HA setup to confirm those steps cause no issues and it would benefit us to cover that type of change.