Description of problem: We were trying to run foreman-tasks-fetch-tasks-status with foreman-tasks-fetch-tasks-status. But for state stopped/planning/pending/scheduled (states other than pending/running), it shows error in foreman-maintain.log as "No count method defined for state". Version-Release number of selected component (if applicable): foreman-maintain snap 3 # rpm -q rubygem-foreman_maintain rubygem-foreman_maintain-0.0.10-1.el7sat.noarch How reproducible:always Steps to Reproduce: 1.# foreman-maintain advanced procedure run foreman-tasks-fetch-tasks-status --state stopped Actual results: # foreman-maintain advanced procedure run foreman-tasks-fetch-tasks-status --state stopped Running ForemanMaintain::Scenario ================================================================================ Fetch tasks status and wait till they finish: / Try checking status of stopped task(s) [OK] -------------------------------------------------------------------------------- But foreman-maintain.log shows I, [2017-10-25 09:20:27-0400 #25041] INFO -- : Running foreman-maintain command with arguments [["advanced", "procedure", "run", "foreman-tasks-fetch-tasks-status", "--state", "stopped"]] E, [2017-10-25 09:20:27-0400 #25041] ERROR -- : No count method defined for state stopped. E, [2017-10-25 09:20:27-0400 #25041] ERROR -- : Unsupported for state stopped. I, [2017-10-25 09:20:27-0400 #25041] INFO -- : foreman-maintain command finished with Expected results:foreman-tasks-fetch-tasks-status should work for all tasks Additional info: foreman-maintain advanced procedure run foreman-tasks-fetch-tasks-status --state pending/running works.
Anurag, what are your thoughts on this one? Should it be targeted to 0.5 or 1.0? Thanks!
We are going to hide foreman-tasks-fetch-tasks-status procedure ( http://projects.theforeman.org/issues/23102 ). So, marking this as NOTABUG.