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.
Description of problem:
Installer fails to configure satellite with external database PostgreSQL when no psql utility installed
Version-Release number of selected component (if applicable):
Satellite 6.10.1.1
How reproducible:
Always
Steps to Reproduce:
1. Configure repos for satellite, and install satellite package.
2. Install and configure postgres on rhel7 box as per documentation[1]
3. Run installer to configure satellite with external db
# satellite-installer --scenario satellite \
--foreman-initial-admin-password <admin-passwd> \
--foreman-db-manage false \
--foreman-db-host $DATABASE \
--foreman-db-database foreman1db \
--foreman-db-username foreman1! \
--foreman-db-password <db-passwd> \
--foreman-db-port 5432 \
--katello-candlepin-manage-db false \
--katello-candlepin-db-host $DATABASE \
--katello-candlepin-db-name candlepin1db \
--katello-candlepin-db-user candlepin1! \
--katello-candlepin-db-password <db-passwd> \
--katello-candlepin-db-port 5432 \
--foreman-proxy-content-pulpcore-manage-postgresql false \
--foreman-proxy-content-pulpcore-postgresql-host $DATABASE \
--foreman-proxy-content-pulpcore-postgresql-db-name pulpcore1db \
--foreman-proxy-content-pulpcore-postgresql-user pulpcore1! \
--foreman-proxy-content-pulpcore-postgresql-password <db-passwd> \
--foreman-proxy-content-pulpcore-postgresql-port 5432
Actual results:
Installer fails in step 3, for missing psql utility
Expected results:
The installer should pass, and should install dependency for psql utility
Additional info:
1. WORKAROUND:
Install package "rh-postgresql12-postgresql-syspaths" on satellite before running the installer and installer pass in step 3.
2. Also tested the same scenario on 6.9.7, it just worked fine, after completion I check `rh-postgresql12-postgresql-syspaths` package was installed after the installer, so looks like a regression to me in 6.10
3. This BZ[2] just provided a fail-safe option for backup/restore for a similar issue.
[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/installing_satellite_server_from_a_connected_network/performing-additional-configuration#using-external-databases_satellite
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1921295
Closing this as NOTABUG after a week of inactivity.
Feel free to reopen if you have a reproducer that does not error out on the PostgreSQL server refusing more connections.