Bug 1496384
Summary: | check for foreman-tasks-not-running is not working | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
Component: | Satellite Maintain | Assignee: | Kavita <kgaikwad> |
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | apatel, bbuckingham, bkearney, inecas, kgaikwad, mmccune, sabnave |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-19 17:22:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1496794 |
Description
Nikhil Kathole
2017-09-27 08:58:45 UTC
Upstream bug assigned to kgaikwad Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21118 has been resolved. 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |