GBP PT delete allows to delete PT , even though the PT is bound to VM
Bug #1523733 reported by
vks1
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
GBP PT delete is succeeding even though the PT is bound to a server. In other way also, if the port associated with PT gets deleted, it triggers PT deletion also. This can affect the chain inconsistency where the nova failed to detach port but GBP still , deletes the PT.
Revision history for this message
| vks1 (vikash-kumar) wrote | #1 |
| Changed in group-based-policy: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| milestone: | none → next |
To post a comment you must log in.
If GBP check for device id of related port before deleting PT, we can solve some inconsistency.