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.
VERIFIED
Version tested:
sat 6.4 snap 21
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.2.9-1.el7sat.noarch
--------------------------------------------------------------------------------
Check whether all services are running using hammer ping: [FAIL]
foreman_tasks resource(s) are failing.
--------------------------------------------------------------------------------
Restart applicable services:
Stopping the following service(s):
dynflowd
\ All services stopped
Starting the following service(s):
dynflowd
- All services started
| Try 1/5: checking status of hammer ping
foreman_tasks resource(s) are failing.
/ Hammer ping returned successfully! [OK]
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check whether all services are running using hammer ping: [OK]
--------------------------------------------------------------------------------
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, 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-2018:2926
Description of problem: Foreman-maintain failed to start foreman-tasks service. Version-Release number of selected component (if applicable): # rpm -qa | grep maintain rubygem-foreman_maintain-0.2.7-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. foreman-maintain service stop --only dynflowd 2. foreman-maintain health check Actual results: # foreman-maintain health check Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check for verifying syntax for ISP DHCP configurations: [OK] -------------------------------------------------------------------------------- Check for paused tasks: [OK] -------------------------------------------------------------------------------- Check whether all services are running using hammer ping: [FAIL] foreman_tasks resource(s) are failing. -------------------------------------------------------------------------------- Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] y Restart applicable services: Stopping the following service(s): [FAIL] No services found matching your parameters -------------------------------------------------------------------------------- Rerunning the check after fix procedure Check whether all services are running using hammer ping: [FAIL] foreman_tasks resource(s) are failing. -------------------------------------------------------------------------------- Continue with step [Restart applicable services]?, [y(yes), n(no), q(quit)] y Restart applicable services: Stopping the following service(s): [FAIL] No services found matching your parameters and foreman-maintain.log showed E, [2018-09-03 02:13:18-0400 #14784] ERROR -- : No services found matching your parameters (RuntimeError) /usr/share/gems/gems/foreman_maintain-0.2.7/definitions/features/service.rb:49:in `filtered_services' /usr/share/gems/gems/foreman_maintain-0.2.7/definitions/procedures/service/base.rb:18:in `run_service_action' /usr/share/gems/gems/foreman_maintain-0.2.7/definitions/procedures/service/restart.rb:17:in `run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/executable.rb:139:in `__run__' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner/execution.rb:83:in `block (2 levels) in run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner/execution.rb:107:in `capture_errors' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner/execution.rb:82:in `block in run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner/execution.rb:101:in `with_metadata_calculation' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner/execution.rb:81:in `run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:116:in `run_step' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:105:in `run_steps' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:98:in `execute_scenario_steps' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:51:in `run_scenario' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:32:in `block in run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:31:in `each' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/runner.rb:31:in `run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/cli/base.rb:47:in `run_scenario' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/cli/health_command.rb:31:in `execute' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:63:in `run' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/subcommand/execution.rb:11:in `execute' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:63:in `run' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/subcommand/execution.rb:11:in `execute' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:63:in `run' /usr/share/gems/gems/foreman_maintain-0.2.7/lib/foreman_maintain/cli.rb:27:in `run' /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:132:in `run' /usr/share/gems/gems/foreman_maintain-0.2.7/bin/foreman-maintain:12:in `<top (required)>' /usr/bin/foreman-maintain:23:in `load' /usr/bin/foreman-maintain:23:in `<main>' Expected results: Restart applicable services should work. Additional info: