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:
While launching the web console of registered client host via Satellite WebUI, blank page opens up and web console dashboard page of the host does not open.
Version-Release number of selected component (if applicable): Satellite 6.12
How reproducible: Always
Steps to Reproduce:
1. Build a RHEL-9 machine and register it with Satellite.
2. Run below command on the registered RHEL-9 client host.
# yum install cockpit
# systemctl enable --now cockpit.socket
# firewall-cmd --add-service=cockpit --permanent
# firewall-cmd --reload
3. Run below command on Satellite machine.
# satellite-installer --enable-foreman-plugin-remote-execution-cockpit
4. Navigate to Satellite WebUI -> Hosts -> All Hosts -> Click on the name of registered client host -> Click on 3 dots at top right corner -> Click on "Web Console".
Actual results: A new completely blank web page gets opened.
Expected results: Red Hat web console dashboard of the host should get opened instead of blank page.
Additional info: The Red Hat web console dashboard of the host can be opened successfully manually using URL: "https://client.example.com:9090"
There seems to be something wrong with your external capsule. If I turn it off (and thus force the connection to go through internal capsule), it works just fine.
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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818
Description of problem: While launching the web console of registered client host via Satellite WebUI, blank page opens up and web console dashboard page of the host does not open. Version-Release number of selected component (if applicable): Satellite 6.12 How reproducible: Always Steps to Reproduce: 1. Build a RHEL-9 machine and register it with Satellite. 2. Run below command on the registered RHEL-9 client host. # yum install cockpit # systemctl enable --now cockpit.socket # firewall-cmd --add-service=cockpit --permanent # firewall-cmd --reload 3. Run below command on Satellite machine. # satellite-installer --enable-foreman-plugin-remote-execution-cockpit 4. Navigate to Satellite WebUI -> Hosts -> All Hosts -> Click on the name of registered client host -> Click on 3 dots at top right corner -> Click on "Web Console". Actual results: A new completely blank web page gets opened. Expected results: Red Hat web console dashboard of the host should get opened instead of blank page. Additional info: The Red Hat web console dashboard of the host can be opened successfully manually using URL: "https://client.example.com:9090"