Bug 2078978 - foreman-maintain health check is unable to restart the qpidd service and failed with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass".
Summary: foreman-maintain health check is unable to restart the qpidd service and fail...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Maintain
Version: 6.10.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-26 15:59 UTC by Gourav Padholia
Modified: 2023-07-17 13:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-17 13:36:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6967446 0 None None None 2022-07-13 08:50:44 UTC

Description Gourav Padholia 2022-04-26 15:59:53 UTC
Description of problem:
foreman-maintain health check is unable to restart the qpidd service and failed with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass".

Version-Release number of selected component (if applicable):
6.10.3

How reproducible:
100%

Steps to Reproduce:
1. Stop the qpidd service manually on the Satellite server. 
2. Run command foreman-maintain health check to check the health of Satellite server. As a result it will show qpidd is failing and press "Y" to restart. 
3. The qpidd service will not restart and it will keep failing with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass".


Actual results:
Qpidd is failing with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass".

Expected results:
Qpidd should be restarted and shouldn't show any error. 

Additional info:

Comment 4 Eric Helms 2023-07-17 13:36:51 UTC
I tested this on Satellite 6.13, and it appears to have been fixed:

[root@ip-10-0-167-238 ~]# foreman-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Clean old Kernel and initramfs files from tftp-boot:                [OK] [2.69]
--------------------------------------------------------------------------------
Check number of fact names in database:                             [OK] [0.07]
--------------------------------------------------------------------------------
Check whether all services are running:                             [FAIL] [0.55]
Following services are not running: qpidd
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no)] y
Restart applicable services:                                                    

Stopping the following service(s):
qpidd
| All services stopped                                                          

Starting the following service(s):
qpidd
/ All services started                                                          
\ Try 1/5: checking status of hammer ping                                       
Some components are failing: katello_agent
/ Try 2/5: checking status of hammer ping                                       
Some components are failing: katello_agent
- Try 3/5: checking status of hammer ping                                       
Some components are failing: katello_agent
| Try 4/5: checking status of hammer ping                                       
Some components are failing: katello_agent
/ Try 5/5: checking status of hammer ping                           [FAIL] [129.39]
Server response check failed!


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