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 2061351 - [RFE] Allow configuration of cockpit configuration via Satellite installer
Summary: [RFE] Allow configuration of cockpit configuration via Satellite installer
Keywords:
Status: CLOSED DUPLICATE of bug 2025892
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.9.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Omkar Khatavkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-07 13:28 UTC by mithun kalyat
Modified: 2022-05-19 14:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-19 14:01:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5040251 0 None None None 2022-03-07 13:29:16 UTC

Description mithun kalyat 2022-03-07 13:28:29 UTC 
Description of problem:

If it's required to use the SAN hostname to access the Satellite WebUI interface and if the Satellite server's custom SSL certificate includes SAN, the following steps need to perform on the Satellite server.

1) Modify /etc/foreman/cockpit/cockpit.conf file and update Origins value:

# cat /etc/foreman/cockpit/cockpit.conf   | head -4
[WebService]
LoginTitle = Foreman Cockpit
UrlRoot = /webcon/
Origins = https://sat6.example.com

2) Edit /etc/foreman/cockpit/foreman-cockpit-session.yml file and replace foreman_url value with SAN hostname:

:foreman_url: "https://sat6.example.com"
:ssl_ca_file: "/etc/pki/katello/certs/katello-server-ca.crt"
:ssl_certificate: "/etc/foreman/client_cert.pem"
:ssl_private_key: "/etc/foreman/client_key.pem"

However the satellite-installer command or an upgrade will override all these and we have to configure again to access the Satellite with the Red Hat web console.


Actual results:

Fails to access the Red Hat web console using CNAME after the upgrade.

Expected results:

Cockpit settings should persists even after the Satellite upgrade.
Comment 1 Eric Helms 2022-05-19 14:01:52 UTC 

*** This bug has been marked as a duplicate of bug 2025892 ***
Comment 2 Eric Helms 2022-05-19 14:24:24 UTC 
Note, you can address this already today by specifying the `--foreman-foreman-url` parameter to the installer.
Note You need to log in before you can comment on or make changes to this bug.