search

StackStorm / st2

StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
https://stackstorm.com/
Apache License 2.0
6.05k stars 745 forks source link

Unhelpful error message when Jinja key doesn't exist #3329

Open Mierdin opened 7 years ago

Mierdin commented 7 years ago

I came across this error when running some release workflows. The cause of this was that our build infrastructure is currently running an older version of StackStorm (which will very soon be remedied via the new ops work), so the st2kv implemented in https://github.com/StackStorm/st2cd/pull/266 was not a thing. However, this error message didn't help me in any way to come to this conclusion - would be nice to see something different here.

oswaltm@st2-build-node-1:~/.ssh$ st2 execution get 58e3245f27263a3ed14c1d20
id: 58e3245f27263a3ed14c1d20
status: failed
parameters:
  distro: UBUNTU16
  hosts: 10.0.3.228
  license_key: dd7b8714ed903cb58754a6860456144638ecc0ad786d6294
  pkg_env: production
  release: stable
  timeout: 120
result:
  error: Dependecy unsatisfied in st2kv
  traceback: "  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2api/controllers/v1/actionexecutions.py", line 154, in _schedule_execution
    liveaction_db.context)
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/util/param.py", line 187, in render_live_params
    _validate(G)
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/util/param.py", line 123, in _validate
    raise ParamException(msg)
"
stale[bot] commented 5 years ago

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.