Bug #25282
closedWrong counts of success/fail/pending tasks on Bulk actions
Description
Description of problem:
Running a bulk action, I get very contradicting stats about overall # tasks, successful/fail/pending/..
E.g. when I run auto-attach against 5 systems where two of them were deleted meantime, I see:
- parent task shows "5 task(s), 3 success, 4 fail"
- sub tasks show 4 success and 4 fail
- dynflow console of the parent task shows:
planned_count: 4
cancelled_count: 0
total_count: 5
failed_count: 4
pending_count: 1
success_count: 3
The failed tasks are two per each of 2 deleted system. Pending count might be consequence of that disbalance, but I already saw 10k total count, 0 failed, 9900 success and 100 pending (while there was no pending, really).
How reproducible:
100%
Steps to Reproduce:
(I expect the problem is more generic but providing a particular reproducer I noticed by myself)
1. Have 5 Content Hosts
2. In WebUI, click to Content Hosts -> select all 5 of them -> Select Action -> Manage Subscriptions
3. Exactly now, unregister 2 from the Content Hosts
4. Now click to Auto-Attach button to trigger the bulk task.
5. wait till the task completes
6. check all possible stats about the bulk action
Actual results:
6. see Description
Expected results:
6. stats to match reality and be aligned to each other
Additional info:
Updated by Adam Ruzicka over 5 years ago
- Subject changed from Wrong counts of success/fail/pending tasks on Bulk actions to Wrong counts of success/fail/pending tasks on Bulk actions
- Category set to Foreman plugin
- Assignee set to Adam Ruzicka
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/371 added
Updated by Adam Ruzicka over 5 years ago
- Pull request https://github.com/Dynflow/dynflow/pull/299 added
Updated by Ivan Necas over 5 years ago
- Status changed from Ready For Testing to Closed