Project

General

Profile

Actions

Bug #30652

closed

Satellite 6.6 to 6.7 upgrade fails on server-ping for rubygem-foreman_maintain-0.6.8-1

Added by Suraj Patil over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1869279

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)

Actions #1

Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/388 added
Actions #2

Updated by Anonymous over 3 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF