Bug 1373895

Summary: Emb->Managed KB: Not true that "you can use any values" when filling in access info
Product: Red Hat Satellite 5 Reporter: Lukáš Hellebrandt <lhellebr>
Component: DocumentationAssignee: Michaela Slaninkova <mslanink>
Status: CLOSED CURRENTRELEASE QA Contact: Russell Dickenson <rdickens>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: rdickens
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-22 09:19:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lukáš Hellebrandt 2016-09-07 11:37:35 UTC
Document URL: https://access.redhat.com/articles/634543

Section Number and Name:
Migrating from an Embedded to a Managed External Database, step 3

Describe the issue: 

The document suggests that "During installation of the managed external database you need to provide the database name, database user and database password details. You can use any values here because the database created during installation of the managed external database will be replaced.".

This is only partly true. The database contents are actually replaced during restoring the backup. However, the document also instructs the user to backup the /var/lib/pgsql/data/pg_hba.conf config file before restoring the database and restore the file after restoring the database. If the user does not restore the file *or if the user fills in other info that the one used on the actual satellite during installation*, the user needs to manually edit the config file and set correct info (otherwise, db-control start will fail silently). When the user fills it correctly during Managed DB installation, this step is not necessary.

The config file editing step is never mentioned in the document. The preferred way woud be IMO to instruct the user to fill in the correct info during installation in the first place.

Comment 1 Lukáš Hellebrandt 2016-09-07 11:54:03 UTC
Related to db-control's silent fail: bug 1373900

Comment 3 Michaela Slaninkova 2017-06-22 09:19:10 UTC
Hello,

I have corrected the misleading information in the article as suggested in the description of this BZ ticket. Therefore, I am closing this BZ ticket.