Unhelpful error message when Jinja key doesn't exist
Open
@lakshmi-kannan is already working on this.
Since Apr 19, 2017.
complexity:easy
good first issue
stale
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
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)
"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.