-
Bug
-
Resolution: Done-Errata
-
Major
-
rhos-18.0 FR 2 (Mar 2025)
-
None
-
3
-
False
-
-
False
-
?
-
openstack-watcher-10.0.1-18.0.20250609094712.c014f81.el9ost
-
rhos-workloads-evolution
-
None
-
-
Bug Fix
-
Done
-
-
-
Workload Evolution Sprint 4, Workload Evolution Sprint 5
-
2
-
Important
When one or more of the Actions included in an Action Plan finishes with FAILED status, the Action Plan still reports SUCCEEDED status.
According to the documentation https://docs.openstack.org/watcher/latest/architecture.html#state-machine-diagrams SUCCEDED means that "the Action Plan has been executed successfully (i.e. all Actions that it contains have been executed successfully)" so in those cases de Action Plan should be reported as FAILED.
To Reproduce Steps to reproduce the behavior:
- Create an audit with a parameter that forces action failure, i.e. unexisting compute node as backup host in the host_maintenance strategy.
- Run de audit
- Start the action plan
- The action fails
- The action plan is marked as SUCCEEDED
Expected behavior
- The action plan should be marked as FAILED
Bug impact
- User will not see the real action plan result when an action fails.
Known workaround
- User can check the status of each action in an action plan manually using openstack cli or horizon watcher dashboard.
- links to
-
RHBA-2025:152056 Release of components for RHOSO 18.0
- mentioned on