AdHoc actions with invalid base definitions fail in the engine but leave the task/workflow running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Undecided
|
Bob Haddleton |
Bug Description
When an AdHoc action has an invalid base defined, execution of the action within a workflow will fail but leave the task and workflow in the RUNNING state. The only indication of the failure is the exception in the mistral log file.
The problem is that the DBEntityNotFoun
The solution is to catch the DBEntityNotFoun
The same problem occurs for nested AdHoc Actions, when any of the nested base actions are invalid.
This is a sample trace from running a test with an invalid adhoc action, without the fix applied:
Traceback (most recent call last):
File "/home/
'my_wb.wf6', '')
File "/home/
res = func(*args, **kw)
File "/home/
return f(*args, **kwargs)
File "/home/
params
File "/home/
return f(*args, **kwargs)
File "/home/
params=params
File "/home/
return f(*args, **kwargs)
File "/home/
wf_
File "/home/
return f(*args, **kwargs)
File "/home/
task_
File "/home/
return f(*args, **kwargs)
File "/home/
task.run()
File "/home/
return f(*args, **kwargs)
File "/home/
self._run_new()
File "/home/
return f(*args, **kwargs)
File "/home/
self.
File "/home/
action = self._build_
File "/home/
wf_
File "/home/
self.
File "/home/
return IMPL.get_
File "/home/
result = func(*args, **kw)
File "/home/
"Action definition not found [action_name=%s]" % identifier
mistral.
Changed in mistral: | |
assignee: | nobody → Bob Haddleton (bob-haddleton) |
status: | New → In Progress |
description: | updated |
description: | updated |
Changed in mistral: | |
milestone: | none → queens-1 |
Fix proposed to branch: master /review. openstack. org/500132
Review: https:/