Bug 1044067

Summary:	katello-configure answer file ignores database username and password options
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Installer	Assignee:	David Davis <daviddavis>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	aspurrie
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-11 16:43:20 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 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