Currently, the applier implements different behaviors when cancelling an action if using threading or eventlet mode. In eventlet mode and depending on the action type, it can try to abort actions which are in ONGOING state. However, in threading mode, it will always wait for the ONGOING actions. This patch is homogenizing the behavior on Cancelling action-plans. Now, it will wait for the running task to complete and cancel all pending actions. This is also simplifying the implementation and cleaning the current mechanism based on killing a separate thread which has scalability and reliability issues. Implements: blueprint remove-cancel-ongoing-actions Change-Id: I7058b32b762de03455d1b082c3cbd5849314350a Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
9 lines
291 B
YAML
9 lines
291 B
YAML
---
|
|
other:
|
|
- |
|
|
Now, when cancelling a running action plan, only the **PENDING** actions
|
|
will be cancelled. The **ONGOING** actions will continue to run until they
|
|
finish.
|
|
|
|
For more details, see: https://blueprints.launchpad.net/watcher/+spec/remove-cancel-ongoing-actions.
|