relict bootstraps spoil deployment

Bug #1422819 reported by Evgeny Kozhemyakin on 2015-02-17
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Fuel Documentation Team

Bug Description

Relict bootstraped nodes (not rebooted) from previous env are recognized by new env but provisioning/deploing fails due to mco_pass mismatch.
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
Bogdan Dobrelya (bogdando) wrote :

Please provide a diagnostic logs snapshot

Changed in fuel:
status: Confirmed → Incomplete
sbartel (samuel-bartel) wrote :

please find attached a corresponding diagnostic snapshot

Changed in fuel:
status: Incomplete → New
Changed in fuel:
status: New → Confirmed
tags: added: docs release-notes
no longer affects: fuel/7.0.x
Vladimir Kuklin (vkuklin) wrote :

This should be covered by docs only. There is no need to create hacks when you can simply reboot nodes with old bootstrap.

tags: added: release-notes-done
removed: release-notes
tags: added: rn7.0
Igor Shishkin (teran) on 2015-10-08
Changed in fuel:
milestone: 7.0 → 8.0
no longer affects: fuel/6.1.x
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-docs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers