python_cmd not set if you use a --start-at-task beyond step 1
Bug #1907858 reported by
Alex Schultz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
Medium
|
Alex Schultz |
Bug Description
We set python_cmd in the step1 file but we use it in every deployment step. If you use --start-at-task and begin at a step > 1, the execution fails with an undefined python_cmd variable when it hits it. You can work around this by including -e python_cmd=python3, however we should set python_cmd near where we use it if not defined.
Changed in tripleo: | |
assignee: | nobody → Alex Schultz (alex-schultz) |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
To post a comment you must log in.
https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/766788