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.
Bug 2096849 - Wrong message for installer step in post-upgrade to 6.11 for regular and non-SSL external DB Satellite setups
Summary: Wrong message for installer step in post-upgrade to 6.11 for regular and non-...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.11.0
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-14 12:21 UTC by Gaurav Talreja
Modified: 2023-02-16 14:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-16 14:31:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15978 0 None None None 2023-02-16 14:01:04 UTC

Description Gaurav Talreja 2022-06-14 12:21:23 UTC 
Description of problem:
An incorrect message appears for the installer step after upgrading to 6.11 both for regular and non-SSL external DB Satellite setups, which is specific to SSL external DB Satellite setup, for more info please check, https://bugzilla.redhat.com/show_bug.cgi?id=2090820#c10 

Version-Release number of selected component (if applicable):
Satellite 6.11.0 Snap 24.0
rubygem-foreman_maintain-1.0.12

How reproducible:
Always

Steps to Reproduce:
1. # foreman-maintain upgrade run --target-version 6.11 --whitelist='repositories-validate,repositories-setup'
..
--------------------------------------------------------------------------------
Run installer with Candlepin SSL CA when using external database with SSL:
| Executing installer                                                 [OK]
--------------------------------------------------------------------------------
..

2. Upon checking if the installer is being run to set this option for regular and non-SSL external DB Satellite setups, this option is UNDEF, which indicates the installer didn't run with this extra option, so this message seems inappropriate here.

# 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)

Actual results:
Wrong message for regular and non-SSL external DB Satellite setups 
"Run installer with Candlepin SSL CA when using external database with SSL:"

Expected results:
Message as similar to previous installer procedure step or something appropriate 

Additional info:
Comment 1 Evgeni Golov 2023-02-16 14:02:30 UTC 
This is only happening during the upgrade to 6.11 (not later versions), so I am inclined to close this as "currentrelease"?
Note You need to log in before you can comment on or make changes to this bug.