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:
Inappropriate error message "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass" is shown when ping pulp3 fails during upgrade from 6.9.4 to 6.10(SNAP 14.0) due to https://bugzilla.redhat.com/show_bug.cgi?id=1996476
Version-Release number of selected component (if applicable):
6.10.0 SNAP14.0
How reproducible:
always
Steps to Reproduce:
1. Continue upgrade after content-switchover fails (as described in BZ#1996476) (maybe some other procedure that causes pulp3 to return 503?)
2. # satellite-maintain upgrade run --target-version 6.10 --whitelist "repositories-validate,repositories-setup,content-switchover"
Actual results:
Following error message is displayed
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [FAIL]
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
--------------------------------------------------------------------------------
Expected results:
Error message should contain something like name of destination server or some different explanation, not "undefined method..."
Additional info:
# tail /var/log/foreman-maintain/foreman-maintain.log
...
D, [2021-08-25 15:58:57-0400 #77043] DEBUG -- : Called /katello/api/ping
D, [2021-08-25 15:58:57-0400 #77043] DEBUG -- : Response: 200, {"status":"FAIL","services":{"candlepin":{"status":"ok","duration_ms":"43"},"candlepin_auth":{"status":"ok","duration_ms":"38"},"foreman_tasks":{"status":"ok","duration_ms":"3"},"katello_events":{"status":"ok","message":"0 Processed, 0 Failed","duration_ms":"0"},"candlepin_events":{"status":"ok","message":"0 Processed, 0 Failed","duration_ms":"0"},"pulp3":{"status":"FAIL","message":"503 Service Unavailable"},"pulp":{"status":"ok","duration_ms":"185"},"pulp_auth":{"status":"ok","duration_ms":"93"}}}
...
# hammer ping
...
pulp3:
Status: FAIL
Server Response: Message: 503 Service Unavailable
...
Verified.
Tested on Satellite 6.10.0 Snap 16.0
Version: rubygem-foreman_maintain-0.8.13-2.el7sat.noarch
Setup:
1. Make pulp3 service fail in `hammer ping` with,
# foreman-maintain service stop --only pulpcore-api,pulpcore-content,pulpcore-worker@1,pulpcore-worker@2,pulpcore-worker@3,pulpcore-worker@4
Steps:
1. # foreman-maintain health check
Observation:
No more inappropriate error message like "undefined method `to_sym' for nil:NilClass" is visible when ping pulp3 fails.
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [FAIL]
Some components are failing: foreman_tasks, pulp3
--------------------------------------------------------------------------------
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