Status of custom_graph execution is always 'ready'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vladimir Sharshov | ||
Future |
Fix Released
|
High
|
Vladimir Sharshov |
Bug Description
MOS9
When some tasks in custom graph fail - the fuel-task is always 'ready'.
Steps to reproduce:
create custom graph with task that will fail deployment:
random.yaml
- id: fail
type: shell
version: 2.1.0
role: ['/.*/']
requires: []
required_for: []
parameters:
cmd: "e=$(echo $RANDOM%2.0 | bc); exit $e"
timeout: 60
fuel2 graph upload --env 1 --type random --file random.yaml
fuel2 graph execute -e 1 -t random
[root@nailgun ~]# fuel2 task history show 8
+------
| task_name | node_id | status | time_start | time_end |
+------
| fail | 7 | error | 2016-09-
| fail | 3 | error | 2016-09-
| fail | 6 | error | 2016-09-
| fail | 2 | error | 2016-09-
| fail | 8 | error | 2016-09-
| fail | 4 | error | 2016-09-
| fail | 5 | error | 2016-09-
| fail | 1 | error | 2016-09-
+------
Actual result:
fuel task:
8 | ready | deployment | 1 | 100 | 2b09e438-
Expected result:
task should have non-ready status, like deployment's one.
[root@nailgun ~]# fuel env
id | status | name | release_id
---+---
1 | partially_deployed | t1 | 2
tags: | added: customer-found |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → 9.1 |
tags: | added: area-python |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Fuel Toolbox (fuel-toolbox) |
tags: | added: on-verification |
Changed in fuel: | |
status: | Fix Committed → Confirmed |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
Can you attach logs for future analysis, at least astute.log?