Unused nodes in Custom Workflow constantly show 1% of progress
Bug #1666192 reported by
Ekaterina Khomyakova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Vladimir Kozhukalov | ||
Newton |
Fix Released
|
High
|
Vladimir Kozhukalov |
Bug Description
Fuel 10 #1355
Steps to reproduce:
1. Log in to Fuel UI
2. Add 1 controller and 1 compute nodes
3. Provision nodes
4. Go to Workflows tab and add custom workflow from json file where there is no "compute" in "groups" section
5. Run custom workflow on nodes
6. Go to Nodes tab
Expected results:
Compute node is in provisioned (or ready?) state
Actual result:
Compute shows progress 1% (see attached picture)
Example of json config:
[
{
"version": "1.0.0",
"id": "task_1",
"task_name": "task_1",
"type": "shell",
"parameters": {
"cmd": "sleep 10",
"timeout": 100
},
"groups": [
"
"controller"
]
}
]
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
status: | New → Confirmed |
tags: | added: area-python |
Changed in fuel: | |
importance: | Medium → High |
tags: | added: blocker-for-qa |
Changed in fuel: | |
status: | Confirmed → Invalid |
Changed in fuel: | |
status: | Invalid → Confirmed |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Vladimir Sharshov (vsharshov) |
Changed in fuel: | |
assignee: | Vladimir Sharshov (vsharshov) → Vladimir Kozhukalov (kozhukalov) |
Changed in fuel: | |
milestone: | 10.1 → 12.0 |
tags: | added: on-verification |
To post a comment you must log in.
We set node progress to 1 when we start the deployment, but we do not set it to 100 if the node has no tasks to run. We do not now which particular node have 0 tasks as graph serialization runs right before casting the message to Astute. This should be fixed on Astute size by sending node progress set to 100 for the nodes that do not have any tasks to run.