Bug 2090820
| Summary: | satellite upgrade to 6.11 fails in installer with "Could not open SSL root certificate file /root/.postgresql/root.crt" error for external DB setup | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Gaurav Talreja <gtalreja> |
| Component: | Installation | Assignee: | Amit Upadhye <aupadhye> |
| Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.11.0 | CC: | aupadhye, egolov, ehelms, pcreech, vijsingh |
| Target Milestone: | 6.11.0 | Keywords: | Regression, Triaged, UpgradeBlocker, Upgrades |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-1.0.12 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-05 14:35:58 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: | |
| Embargoed: | |||
|
Description
Gaurav Talreja
2022-05-26 15:47:44 UTC
Created redmine issue https://projects.theforeman.org/issues/35029 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35029 has been resolved. Hi,
Tested upgrade for Satellite with external DB SSL setup from 6.10.7 to 6.11, and it works perfectly by adding new required flag to the installer step in the 6.11 upgrade scenario.
--------------------------------------------------------------------------------
Run installer with Candlepin SSL CA when using external database with SSL:
- Running installer with --katello-candlepin-db-ssl-ca /usr/share/foreman/root.crt argument!
[OK]
--------------------------------------------------------------------------------
As well, I check upgrades for regular Satellite and Satellite with external DB on non-SSL setup, which also return the below message for the installer step, so I was wondering if anyone knew if this flag is supposed to be set for these setups? if yes, so it is still set to UNDEF after an upgrade, or is it just a message from the description of the procedure?
--------------------------------------------------------------------------------
Run installer with Candlepin SSL CA when using external database with SSL:
| Executing installer [OK]
--------------------------------------------------------------------------------
As you can see, this description/message is misleading for regular and non-SSL Satellite setups, so I believe it should only be modified if `extdb_and_ssl?`, so how do you recommend handling this BZ?
Thanks,
Gaurav
Hello Gaurav, Thanks for testing the change. I feel the current messaging is correct as we also show if installer is getting executed with extra options in both cases. We can change the description of the procedure however I also feel that's the use of the procedure? This should not be the blocker for the GA, if required another bugzilla can be opened to change the description if needed. Regards, Amit Upadhye. Hello Amit, Thanks for looking into this. >> I feel the current messaging is correct as we also show if an installer is getting executed with extra options in both cases. We can change the description of the procedure however I also feel that's the use of the procedure? Looking at the code below I don't think an installer is executed with extra options in both cases, but shouldn't the extra options be specific to extdb_and_ssl? ``` def run if extdb_and_ssl? run_installer_with_extra_option else run_installer end end ``` and if the installer runs with extra options for both cases then I check it is not being set after a successful upgrade to 6.11 for regular and non-SSL external DB Satellite setups # satellite-installer --full-help | grep katello-candlepin-db-ssl-ca --katello-candlepin-db-ssl-ca The CA certificate to verify the SSL connection to the database with (current: UNDEF) --reset-katello-candlepin-db-ssl-ca Reset candlepin_db_ssl_ca to the default value (UNDEF) >> This should not be the blocker for the GA, if required another bugzilla can be opened to change the description if needed. Yes, I totally agree with you. I've opened a BZ to track this description issue separately BZ 2096849. Hence verifying this BZ for Satellite 6.11.0 Snap 24.0 with version rubygem-foreman_maintain-1.0.12-1.el7sat.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498 |