Mistral can be too limiting regarding action output length
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dougal Matthews |
Bug Description
When running Ansible via a Mistral action, it's fairly easy to hit the size limits in Mistral for stdout length. The error message looks as such:
2017-09-19 12:31:40.140 21170 INFO workflow_trace [-] Task 'deploy_kubernetes' (7433eeee-
Traceback (most recent call last):
File "/usr/lib/
action.
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib64/
instance_
File "/usr/lib64/
value, old, initiator)
File "/usr/lib64/
self.
File "/usr/lib64/
fn(target, value, *arg)
File "/usr/lib/
lambda t, v, o, i: validate_
File "/usr/lib/
size_limit_kb
SizeLimitExceed
] (execution_
So far the workaround has been to run ansible with `verbosity: 0`.
Regardless of this particular use case, it may be worth evaluating if Mistral action output limits shouldn't be higher.
no longer affects: | mistral |
Changed in tripleo: | |
assignee: | nobody → Dougal Matthews (d0ugal) |
status: | Triaged → In Progress |
I removed Mistral as it is already configurable, so just a tripleo issue.