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:
Error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
" while running server-ping.
Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 6
- rubygem-foreman_maintain-0.6.5-1.el7sat.noarch
How reproducible:
- Always
Steps to Reproduce:
1. Run "foreman-maintain health check --label server-ping"
Actual results:
foreman-maintain health check --label server-ping
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check whether all services are running using the ping call: [FAIL]
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] y
Restart applicable services:
Stopping the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, rh-redis5-redis, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
- stopping foreman
Warning: Stopping foreman.service, but it can still be activated by:
foreman.socket
| All services stopped
Starting the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, rh-redis5-redis, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
- All services started
/ Try 1/5: checking status of hammer ping
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
/ Try 2/5: checking status of hammer ping
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
| Try 3/5: checking status of hammer ping
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
| Try 4/5: checking status of hammer ping
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
| 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]
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] n
Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] q
Scenario [ForemanMaintain::Scenario::FilteredScenario] 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:
Server-ping should work properly.
Additional info: