Feature #16993

Running jobs that resolve to 0 hosts result as 'succeeded'

Added by Adam Ruzicka 6 months ago. Updated 6 months ago.

Status:New
Priority:Low
Assigned To:-
Category:-
Target version:Foreman - Team Ivan backlog
Difficulty: Pull request:
Bugzilla link:1371279
Story points-
Velocity based estimate-

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1371279

Description of problem:
If we run a remote execution job that has a 'search query' which resolves to 0 hosts, the job will still run but show a mis-leading success.

Version-Release number of selected component (if applicable):
Satellite 6.2.1:
rubygem-smart_proxy_remote_execution_ssh-0.1.2-2.el7sat.noarch
tfm-rubygem-smart_proxy_remote_execution_ssh_core-0.1.2-1.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. Goto Monitor -> Jobs
2. Click Run Job
3. Create a search query that resolves to 0 hosts, for example:
last_report < "30 minutes ago" and status.enabled = false
4. Submit job.

Actual results:
Shows evaluated against 0 hosts, but shows succeeded on right side (where we normally see percentage complete for job run).
Hosts tab is empty.
Monitor -> Jobs shows a job with 0 total hosts, and 0 actions, with status 'succeeded'.

Expected results:
Should not allow job to run if it resolves to 0 hosts on job submission.

History

#1 Updated by Adam Ruzicka 6 months ago

  • Target version set to Team Ivan backlog

Also available in: Atom PDF