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:
Capsule upgrade fails if goferd service is stopped
Version-Release number of selected component (if applicable):
6.9.3
How reproducible:
Every time
Steps to Reproduce:
1. Turn off goferd
2. Upgrade capsule from 6.9.2 to 6.9.3
3.
Actual results:
--------------------------------------------------------------------------------
Check whether all services are running: [FAIL]
Following services are not running: goferd
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]? (assuming yes)
Restart applicable services:
Stopping the following service(s): [FAIL]
No services found matching your parameters
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check whether all services are running: [FAIL]
Following services are not running: goferd
--------------------------------------------------------------------------------
Expected results:
- goferd on capsule requirement needs to be evaluated as it is being deprecated on all Satellite hosts
- if goferd is required
-- goferd service should be included in the restart of capsule services
- if goferd is not required
-- goferd service should not be checked in the installer/upgrade process
Additional info:
if goferd is not required, steps 1 and 2 need to be removed from the Capsule update documentation:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-single/upgrading_and_updating_red_hat_satellite/index#updating_capsule_server_to_next_minor_version
The output looks like something coming out of foreman maintain. Capsule (as a specific deployment of smart-proxy with plugins) cannot really do anything about this.
Reproduced on Capsule 6.9.5 snap 3 with rubygem-foreman_maintain-0.7.12-1.el7sat.noarch and goferd disabled
Verified on Capsule 6.9.5 snap 3 with rubygem-foreman_maintain-0.8.10-1.el7sat.noarch from 6.10.0 snap 14:
1) upgrade check without gofer installed passed OK
2) upgrade check with gofer installed and disabled passed OK
3) upgrade check with gofer installed and running passed OK
4) upgrade run to 6.9.z with gofer installed and disabled passed OK
Running Checks before upgrading to Capsule 6.9.z
================================================================================
Check to verify no empty CA cert requests exist: [OK]
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [OK]
--------------------------------------------------------------------------------
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.10 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:4697