Bug #22187: when I delete hosts where remote job was running, that finished remote job will start showing >100% result - Foreman Remote Execution - Foreman

Actions

Copy link

Bug #22187

closed

when I delete hosts where remote job was running, that finished remote job will start showing >100% result

Added by Adam Ruzicka about 7 years ago. Updated over 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Foreman

Target version:

Difficulty:

Triaged:

Bugzilla link:

1531536

Pull request:

https://github.com/theforeman/foreman_remote_execution/pull/528, https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/34, https://github.com/theforeman/foreman_remote_execution/pull/309

Fixed in Releases:

foreman_remote_execution 4.1.0, hammer_cli_foreman_remote_execution 0.2.0

Found in Releases:

Red Hat JIRA:

Description

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

Description of problem:
When I delete hosts where remote job was running, that finished remote job will start showing >100% result

Version-Release number of selected component (if applicable):
satellite-6.3.0-23.0.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Run ReX job on 10 systems so it passes on all of them
2. Job detail page now shows "100% success" in the graph
https://<fqdn>/job_invocations/<id>
3. Delete few of these hosts and recheck the ReX job status

Actual results:
120% success

Expected results:
Percentage should be max 100%

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Adam Ruzicka about 7 years ago

Category set to Foreman
Target version set to 113

Actions

Copy link

Updated by The Foreman Bot about 7 years ago

Status changed from New to Ready For Testing
Assignee set to Anonymous
Pull request https://github.com/theforeman/foreman_remote_execution/pull/309 added