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.
Revision history for this message
| Robert Kukura (rkukura) wrote | #1 |
| Changed in group-based-policy: | |
| status: | New → Confirmed |
| Changed in group-based-policy: | |
| importance: | Undecided → High |
| assignee: | nobody → Sumit Naiksatam (snaiksat) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to group-based-policy (master) | #2 |
| Changed in group-based-policy: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (master) | #3 |
| Changed in group-based-policy: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to group-based-policy (stable/juno) | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (stable/juno) | #5 |
| tags: | added: in-stable-juno |
| 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.