Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1450492 - Create the .pgpass and print required conf for standby on primary database servers
Create the .pgpass and print required conf for standby on primary database se...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.7.0
Unspecified Unspecified
unspecified Severity medium
: GA
: 5.8.0
Assigned To: Gregg Tanzillo
luke couzens
HA:black
: ZStream
Depends On:
Blocks: 1450508
  Show dependency treegraph
 
Reported: 2017-05-12 14:33 EDT by Nick Carboni
Modified: 2017-05-31 11:12 EDT (History)
6 users (show)

See Also:
Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1450508 (view as bug list)
Environment:
Last Closed: 2017-05-31 11:12:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1367 normal SHIPPED_LIVE Moderate: CFME 5.8.0 security, bug, and enhancement update 2017-05-31 14:16:03 EDT

  None (edit)
Description Nick Carboni 2017-05-12 14:33:56 EDT
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
Comment 2 Nick Carboni 2017-05-12 14:36:47 EDT
This is already in 5.8 and master so changing the flags to be a 5.7 only issue
Comment 4 luke couzens 2017-05-22 17:08:26 EDT
Verified in 5.8.0.15
Comment 6 errata-xmlrpc 2017-05-31 11:12:29 EDT
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

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