relict bootstraps spoil deployment
Bug #1422819 reported by
Evgeny Kozhemyakin
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Documentation Team | ||
Bug Description
Relict bootstraped nodes (not rebooted) from previous env are recognized by new env but provisioning/
We need to tie such bootstraps to master / force reboot / prevent them from getting in "discovered".
| Changed in fuel: | |
| milestone: | none → 6.1 |
| assignee: | nobody → Fuel Library Team (fuel-library) |
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Incomplete |
Revision history for this message
| sbartel (samuel-bartel) wrote | #2 |
| Changed in fuel: | |
| status: | Incomplete → New |
| Changed in fuel: | |
| status: | New → Confirmed |
| tags: | added: docs release-notes |
| no longer affects: | fuel/7.0.x |
Revision history for this message
| Vladimir Kuklin (vkuklin) wrote | #3 |
| tags: |
added: release-notes-done removed: release-notes |
| tags: | added: rn7.0 |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| no longer affects: | fuel/6.1.x |
| tags: | added: area-docs |
To post a comment you must log in.
Please provide a diagnostic logs snapshot