Update PTG fails with PortNotFound
Bug #1467159 reported by
Sumit Naiksatam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy |
Fix Released
|
High
|
Sumit Naiksatam |
Bug Description
The following code block:
https:/
does not check if there is no port associated with a PT, and the update fails if there is none. Probably a check similar to that in the disassociate SG code block:
https:/
should be performed.
Changed in group-based-policy: | |
importance: | Undecided → High |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
Changed in group-based-policy: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As I recall, the resource_mapping driver was written with the expectation that PTs always have valid ports. Given that race conditions, failures during postcommit, and port deletion using neutron are all possible, I agree the code should be defensive, and the two cited cases should be handled similarly.