leak Vm when recover node failed
Bug #1820838 reported by
Thai Nguyen Ngoc
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| senlin |
Fix Released
|
Critical
|
Thai Nguyen Ngoc | ||
Bug Description
Hi all,
When creating new node is failed, I recover node but also failed.
Now new vm (VM1) is created but physical_id of node have not updated.
And I recover node again, VM1 is not deleted, but a new Vm (VM2) is created.
Result in VM1 is leaked.
| Changed in senlin: | |
| assignee: | nobody → XueFeng Liu (jonnary-liu) |
| assignee: | XueFeng Liu (jonnary-liu) → nobody |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to senlin (master) | #1 |
| Changed in senlin: | |
| status: | New → Fix Released |
| Changed in senlin: | |
| importance: | Undecided → Critical |
| assignee: | nobody → Thai Nguyen Ngoc (thainn2) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/senlin 8.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 23fd8b3954601be
Author: Thai Nguyen Ngoc <email address hidden>
Date: Tue Mar 19 17:42:18 2019 +0700
fix leaks VM when creating node failured
This patch update physical_id of node even in case recover node failured
if Vm is created.
Change-Id: I8a8bc60913f561
Closes-Bug: #1820838