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:
Satellite 6.6 to 6.7 upgrade fails on server-ping for rubygem-foreman_maintain-0.6.8-1.el7sat.noarch
Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 11
- rubygem-foreman_maintain-0.6.8-1.el7sat.noarch
How reproducible:
- Always
Steps to Reproduce:
1. Install Satellite 6.6
2. Install rubygem-foreman_maintain-0.6.8-1.el7sat.noarch
3. Perform Satellite 6.6 to 6.7 upgrade
Actual results:
Running Checks after upgrading to Satellite 6.7
================================================================================
Clean old Kernel and initramfs files from tftp-boot: [OK]
--------------------------------------------------------------------------------
Check number of fact names in database: [OK]
--------------------------------------------------------------------------------
Check for verifying syntax for ISP DHCP configurations: [OK]
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]? (assuming yes)
Restart applicable services:
Stopping the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, tomcat, httpd
| All services stopped
Starting the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, tomcat, httpd
/ All services started
\ Try 1/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth, foreman_tasks
\ Try 2/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth, foreman_tasks
\ Try 3/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth, foreman_tasks
\ Try 4/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth, foreman_tasks
\ Try 5/5: checking status of hammer ping [FAIL]
Server response check failed!
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp, pulp_auth, candlepin, candlepin_auth, foreman_tasks
--------------------------------------------------------------------------------
Check still failing after attempt to fix. Skipping
Check for paused tasks: [OK]
--------------------------------------------------------------------------------
Check to verify no empty CA cert requests exist: [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------
Check if only installed assets are present on the system:
| Checking for presence of non-original assets... [OK]
--------------------------------------------------------------------------------
Scenario [Checks after upgrading to Satellite 6.7] failed.
The following steps ended up in failing state:
[server-ping]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="server-ping"
--------------------------------------------------------------------------------
Expected results:
- Satellite upgrade completed successfully.
Additional info:
- On product page after satellite upgrade I see:
Oops, we're sorry but something went wrong Katello::Resources::Candlepin::Owner: 404 Not Found (GET /candlepin/owners/Default_Organization)
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.8 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-2020:4365
Comment 11Red Hat Bugzilla
2023-09-15 00:46:26 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days