The traits associations are deleted incorrectly
Bug #1708978 reported by
Alex Xu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Alex Xu | ||
Bug Description
For example, Both ResourceProvider1 and ResourceProvider2 have trait CUSTOM_TRAIT_A. When detaching the CUSTOM_TRAIT_A from the ResourceProvider2, the association between CUSTOM_TRAIT_A and ResourcePRovider1 should be kept. But The current code removes the all the associations with CUSTOM_TRAIT_A.
| Changed in nova: | |
| assignee: | nobody → Alex Xu (xuhj) |
| Changed in nova: | |
| status: | New → In Progress |
| tags: | added: placement |
| Changed in nova: | |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/nova 16.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e66c1accbd2ecbc
Author: He Jie Xu <email address hidden>
Date: Mon Jul 31 21:07:17 2017 +0800
placement: filtering the resource provider id when delete trait association
When delete a trait association for specific resource provider, the current
code will delete that trait associations for all the resource providers.
The expected behaviour is only the specific trait association for the
specific resource provider will be removed. This patch corrects the filter
for the deletion of trait association.
Change-Id: I4b8f1b8f0a8d16
Closes-Bug: #1708978