Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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