astute could skip removing of a node from cobbler if requested to remove more than 7 nodes at once.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Vladimir Kozhukalov | ||
7.0.x |
Fix Released
|
Critical
|
Vladimir Kozhukalov | ||
8.0.x |
Fix Released
|
Critical
|
Vladimir Kozhukalov |
Bug Description
ISO 288 (RC2)
It's hard to reproduce this bug but I caught it twice (of about 5, the last was caught on fresh env after first deployment).
Steps for me:
1) Deploy 2 clusters:
First: HA with detached-database node - https:/
Second: Simple with detached-keystone - https:/
2) Delete both clusters
3) Wait until all nodes becomes available
Actual result:
1 node was not bootstrapped, http://
This but is probably related to https:/
I will keep my env - feel free to request access
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Aleksandr Gordeev (a-gordeev) |
tags: | added: module-astute |
summary: |
- After cluster deletion node can't bootstrap - "boot sector signature not - found, (unbootable disk/partition?)" + astute could skip removing of a node from cobbler if requested to remove + more than 7 nodes at once. |
tags: | added: on verification |
tags: | added: on-verification |
tags: | added: area-python |
Also reproduced after upgrade from 6.1 to 7.0 with 288 tarball.
Delete existing cluster created in 6.1 and 1 node doesn't boostrapped.
Only "virsh destroy" + "virsh start" help's