[astute] If puppet fails with dependency graph, fuel can't determine it
Bug #1326583 reported by
Andrey Grebennikov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Vladimir Sharshov |
Bug Description
If I change manifests and make a mistake, or in any other case if the deployment failed on the node with multiple roles assigned, puppet returns 0 as an exit code. Consequently Fuel continue deployment specifying the next assigned role to the node.
Seems something has been fixed in puppet.
no longer affects: | fuel/4.1.x |
no longer affects: | fuel |
summary: |
- Fuel continues deploy next role if previous failed + If puppet fails with dependency graph, fuel can't determine it |
no longer affects: | fuel/5.0.x |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Astute Team (fuel-astute) |
milestone: | none → 5.1 |
no longer affects: | mos |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
assignee: | Fuel Astute Team (fuel-astute) → Vladimir Sharshov (vsharshov) |
tags: | added: astute |
Changed in fuel: | |
assignee: | Fuel OSCI Team (fuel-osci) → Vladimir Sharshov (vsharshov) |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
milestone: | 6.1 → 6.0 |
importance: | Medium → Critical |
status: | Confirmed → Triaged |
Changed in fuel: | |
status: | Triaged → Fix Committed |
tags: | added: on-verification |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
tags: | removed: on-verification |
To post a comment you must log in.
This usually happens when puppet is evaluating the dependency graph and dies due for some reason, In this case puppet will return 0 and astute thinks it done. This is confirmed on puppet 2.7. We need to verify if this applies to puppet 3.4, If so it needs to be accommodated for.