Bug 1869279 - Satellite 6.6 to 6.7 upgrade fails on server-ping for rubygem-foreman_maintain-0.6.8-1
Summary: Satellite 6.6 to 6.7 upgrade fails on server-ping for rubygem-foreman_maintai...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.8.0
Assignee: Suraj Patil
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 11:59 UTC by Jameer Pathan
Modified: 2023-09-15 00:46 UTC (History)
5 users (show)

Fixed In Version: rubygem-foreman_maintain-0.6.10
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:38:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30652 0 High Closed Satellite 6.6 to 6.7 upgrade fails on server-ping for rubygem-foreman_maintain-0.6.8-1 2021-01-24 22:57:02 UTC
Red Hat Product Errata RHBA-2020:4365 0 None None None 2020-10-27 12:38:59 UTC

Description Jameer Pathan 2020-08-17 11:59:50 UTC
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)

Comment 2 Suraj Patil 2020-08-17 12:10:10 UTC
Created redmine issue https://projects.theforeman.org/issues/30652 from this bug

Comment 5 Bryan Kearney 2020-08-31 20:01:34 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30652 has been resolved.

Comment 6 Patrick Creech 2020-09-01 20:11:24 UTC
Hello,

Can we get a 0.6.z upstream release of foreman_maintain with this fix in it?

Thanks,
Patrick

Comment 7 Jameer Pathan 2020-09-15 06:10:36 UTC
Verified

Verified with:
- Satellite 6.8 snap 15
- rubygem-foreman_maintain-0.6.10-1.el7sat.noarch

Test steps:
1. Install Satellite 6.6
2. Install rubygem-foreman_maintain-0.6.10-1.el7sat.noarch
3. Perform Satellite 6.6 to 6.7 upgrade

Observation:
- Satellite upgrade completed successfully.

Comment 10 errata-xmlrpc 2020-10-27 12:38:46 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.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 11 Red 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


Note You need to log in before you can comment on or make changes to this bug.