Delete Cluster fails when Cluster contains VM's which have already been deleted
Bug #1469823 reported by
Davide Agnello
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cue |
Fix Committed
|
High
|
Davide Agnello | ||
Bug Description
When a cluster creation takes place, nodes (VMs) are created in 'parallel' task flows. When VMs go to active state, corresponding node DB records get updated with VM id. If cluster creation fails after any Node records have been updated, any subsequent cluster delete will fail because 'list ports on VM' does not handle Nova not found exception.
This scenario can happen when:
* RabbitMQ does not cluster
* resources get exhausted therefore not all VMs are created
| Changed in cue: | |
| importance: | Undecided → Critical |
| importance: | Critical → High |
| Changed in cue: | |
| status: | New → Confirmed |
| assignee: | nobody → Davide Agnello (dagnello) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cue (master) | #1 |
| Changed in cue: | |
| status: | Confirmed → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 04761d3444e4813
Author: dagnello <email address hidden>
Date: Fri Jun 26 20:05:30 2015 -0700
Delete Cluster Bug
closes-bug: 1469823
Change-Id: If3a6b861dcecd6