Bug 1044067 - katello-configure answer file ignores database username and password options
Summary: katello-configure answer file ignores database username and password options
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 17:59 UTC by Mike McCune
Modified: 2014-06-19 19:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-11 16:43:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Mike McCune 2013-12-17 17:59:55 UTC
If a user specifies a Postgres username and password in katello-configure's answerfile it will not be used when initializing the database.

If the user strays from:

# objects.
db_name = katelloschema

# Katello database user.
db_user = katellouser

# Katello database password.
db_password = katellopw

to say something like:

# objects.
db_name = katelloschema

# Katello database user.
db_user = someuser1

# Katello database password.
db_password = password2

the configuration files for Katello will be written with 'someuser1' and a hashed 'password2' but the actual database still gets initialized with katellouser/katellopw

This causes Katello's Rails app to fail to connect to the Katello PG database

Comment 2 Bryan Kearney 2014-03-11 16:43:20 UTC
Closing old bugs which are not relevant based on new UI and CLI


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