The steps to reintroduce a failed primary node are too long and error prone. Specifically steps 3 and 4 could be removed from https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.2/html/configuring_high_availability/database_failover#reintroducing_the_failed_node if we just printed that information on both primary and standby configuration (it won't hurt anything on the primary). https://github.com/ManageIQ/manageiq-gems-pending/pull/1
This is already in 5.8 and master so changing the flags to be a 5.7 only issue
Verified in 5.8.0.15
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1367