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: we were trying to fail foreman-tasks-not-running health check and thus run a task from UI.But found that foreman-tasks-not-running health check still pass giving result "Check for running tasks: [OK]".
Version-Release number of selected component (if applicable): Foreman-maintain 2.0
How reproducible: always
Steps to Reproduce:
1. Run a task from UI (Make sure it is in running state)
2.# foreman-maintain health check --label foreman-tasks-not-running
Actual results:
Check will pass and foreman-maintain.log shows
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q satellite with stdin nil
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command:
satellite-6.3.0-18.0.beta.el7sat.noarch
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'foreman' --queryformat="%{VERSION}" with stdin nil
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command:
1.15.4.1
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'ruby193-rubygem-foreman-tasks' --queryformat="%{VERSION}" with stdin nil
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command:
package ruby193-rubygem-foreman-tasks is not installed
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'tfm-rubygem-foreman-tasks' --queryformat="%{VERSION}" with stdin nil
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command:
0.9.4
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q satellite with stdin nil
D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command:
satellite-6.3.0-18.0.beta.el7sat.noarch
I, [2017-09-27 04:51:33-0400 #84954] INFO -- : Running foreman-maintain command with arguments [["health", "check", "--label", "foreman-tasks-not-running"]]
I, [2017-09-27 04:51:33-0400 #84954] INFO -- : foreman-maintain command finished with
Expected results:
When task is in running state, health check for foreman-tasks-not-running should fail.
Additional info:
Comment 1Satellite Program
2017-10-17 12:24:23 UTC
Upstream bug assigned to kgaikwad
Comment 2Satellite Program
2017-10-18 16:24:52 UTC
VERIFIED
Version Tested:
# rpm -q rubygem-foreman_maintain
rubygem-foreman_maintain-0.1.1-1.el7sat.noarch
# foreman-maintain health check --label foreman-tasks-not-running
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check for running tasks: [FAIL]
There are 2 active task(s) in the system.
Please wait for these to complete or cancel them from the Monitor tab.
--------------------------------------------------------------------------------
There are multiple steps to proceed:
1) Fetch tasks status and wait till they finish
2) Investigate the tasks via UI
Select step to continue, [n(next), q(quit)]
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:0330
Description of problem: we were trying to fail foreman-tasks-not-running health check and thus run a task from UI.But found that foreman-tasks-not-running health check still pass giving result "Check for running tasks: [OK]". Version-Release number of selected component (if applicable): Foreman-maintain 2.0 How reproducible: always Steps to Reproduce: 1. Run a task from UI (Make sure it is in running state) 2.# foreman-maintain health check --label foreman-tasks-not-running Actual results: Check will pass and foreman-maintain.log shows D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q satellite with stdin nil D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command: satellite-6.3.0-18.0.beta.el7sat.noarch D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'foreman' --queryformat="%{VERSION}" with stdin nil D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command: 1.15.4.1 D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'ruby193-rubygem-foreman-tasks' --queryformat="%{VERSION}" with stdin nil D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command: package ruby193-rubygem-foreman-tasks is not installed D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q 'tfm-rubygem-foreman-tasks' --queryformat="%{VERSION}" with stdin nil D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command: 0.9.4 D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : Running command rpm -q satellite with stdin nil D, [2017-09-27 04:51:33-0400 #84954] DEBUG -- : output of the command: satellite-6.3.0-18.0.beta.el7sat.noarch I, [2017-09-27 04:51:33-0400 #84954] INFO -- : Running foreman-maintain command with arguments [["health", "check", "--label", "foreman-tasks-not-running"]] I, [2017-09-27 04:51:33-0400 #84954] INFO -- : foreman-maintain command finished with Expected results: When task is in running state, health check for foreman-tasks-not-running should fail. Additional info: