Bug #25541
closedSingleton actions may not start after unclean shutdown
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1652060
Description of problem:
We trigger singleton actions (LOCE, EQM) from dynflow's on_init hook. Recently we moved invalidation to happen after running the hooks. It is now possible to get into a situation where
1) On init hook is run, singleton actions fail because a lock is being held by another execution plan
2) Invalidation is performed, old actions fail with abnormal termination error and their locks are released
3) The satellite is left without LOCE and EQM
We used to do steps 1 and 2 in reverse order which worked, but changed that because of another issue.
How reproducible:
always
Steps to Reproduce:
0. (optional) Patch LOCE to make this easier to reproduce, add a lengthy sleep into its run method
1. systemctl kill --signal=9 foreman-tasks when the singleton action's step is running
2. systemctl restart foreman-tasks
Actual results:
New singleton actions fail with "$ACTION_CLASS is already active", old singleton actions fail with abnormal termination error, satellite is left without LOCE and EQM.
Expected results:
Old singleton actions get cleaned up, new are started.
Additional info:
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/Katello/katello/pull/7848 added
Updated by Adam Ruzicka over 5 years ago
- Subject changed from Singleton actions may not start after unclean shutdown to Singleton actions may not start after unclean shutdown
- Pull request https://github.com/Dynflow/dynflow/pull/307 added
Updated by Christine Fouant over 5 years ago
- Target version set to Katello 3.9.1
- Triaged changed from No to Yes
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|c23ae22b7d82fc35e277fb6aad3ae167e706472f.