Bug #18522

Rerun failed hosts creates a new job invocation instead of updating the existing job invocation

Added by Adam Ruzicka over 1 year ago. Updated over 1 year ago.

Assigned To:-
Target version:Foreman - Team Ivan backlog
Difficulty: Pull request:
Bugzilla link:1386197
Story points-
Velocity based estimate-


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

Description of problem:
When i select rerun failed hosts the job invocation is not updated with the new result. Instead a new job invocation is created for the failed hosts.

From a user point of view my expectation is a 'rerun' means to re-run it in the context of the same invocation and update the results of that job invocation.
With the current design to create a new invocation the overall result of the job is lost, because as an user i have now to overlay the results of multiple job invocations to see the total result.

For a good and user friendly reference implementation see Atlassian Bamboo how it handles run incomplete or failed or rerun.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run job template on 5 hosts, make sure 3 hosts will fail
2. Fix the 3 failing hosts to make sure the job succeeds
2. Click rerun failed templates

Actual results:
A new job invocation is started for the 3 failed hosts

Expected results:
The current job invocation is updated and shows 100% success

Additional info:


#1 Updated by Adam Ruzicka over 1 year ago

  • Target version set to Team Ivan backlog

Also available in: Atom PDF