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 1876220 - foreman-cockpit is not restarted with satellite-maintain restart
Summary: foreman-cockpit is not restarted with satellite-maintain restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.9.0
Assignee: Suraj Patil
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-06 13:46 UTC by Calvin Smith
Modified: 2022-03-07 10:22 UTC (History)
9 users (show)

Fixed In Version: rubygem-foreman_maintain-0.7.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 14:48:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30848 0 Normal Closed foreman-cockpit is not restarted with satellite-maintain restart 2021-01-18 08:40:04 UTC
Github SatelliteQE robottelo pull 9293 0 None Merged Add test coverage for BZ#1876220 2022-03-07 10:22:32 UTC
Red Hat Product Errata RHBA-2021:1312 0 None None None 2021-04-21 14:48:34 UTC

Description Calvin Smith 2020-09-06 13:46:28 UTC 
Description of problem:
the cockpit-ws connection that the satellite server uses for the web console is not restarted with satellite-maintain restart

Version-Release number of selected component (if applicable):


How reproducible:
easily

Steps to Reproduce:
1. On satellite: pkill -f cockpit-ws
2. Try to go to web console on managed server, get 503 error
3. Satellite-maintain services restart to restart the satellite server
4. web console is still down
5. Have to manually run systemctl start foreman-cockpit to restart it

Actual results:
if foreman-cockpit dies, get 503 error on webconsole after satellite restart

Expected results:
webconsole functions normally

Additional info:
Comment 1 Adam Ruzicka 2020-09-15 07:53:35 UTC 
Changing component to foreman maintain since we can't really control what f-m does from rex.
Comment 2 Suraj Patil 2020-09-15 13:14:51 UTC 
Created redmine issue https://projects.theforeman.org/issues/30848 from this bug
Comment 3 Bryan Kearney 2020-12-04 16:04:00 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30848 has been resolved.
Comment 4 Gaurav Talreja 2021-01-20 07:21:44 UTC 
Verified.

Tested on Satellite 6.9.0 Snap 9
Version: rubygem-foreman_maintain-0.7.4-1.el7sat.noarch

Setup:
1. # satellite-installer --enable-foreman-plugin-remote-execution-cockpit
2. Setup HTTP-proxy and ssh pub key for REX to access the Web console.
3. In the Satellite web UI, navigate to Hosts > All Hosts, select the host, and click on Web Console to verify if foreman_cockpit is working.
4. If trying to access Satellite cockpit console, then Set 'Fallback to Any Capsule' to YES in WebUI settings in RemoteExecution.

Steps:
1. On satellite: pkill -f cockpit-ws
2. Try to go to web console on a managed server, get 503 error
3. "satellite-maintain service list" to check if service "foreman-cockpit.service" exists.
4. "satellite-maintain service restart" to restart the satellite services.

Observation:
foreman_cockpit service is listed in step3 stdout, and after service restart in step4, the Web console is accessible again.
Comment 7 errata-xmlrpc 2021-04-21 14:48:22 UTC 
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 (Satellite 6.9 Satellite Maintenance 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/RHBA-2021:1312
Note You need to log in before you can comment on or make changes to this bug.