Pool member to real server association logic is broken
Bug #1418840 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
Current the first n PTs in the Provider PTG are used to associate with the n Pool Members in a LB config. However, if there are other PTs present in the same PTG (which are not meant to the real servers), they can erroneously be associated with the Pool Member.
Also, if no Neutron port is associated with the PT, the entire service configuration fails. In such cases, ideally the PT should be skipped.
| Changed in group-based-policy: | |
| status: | Confirmed → In Progress |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-1 → kilo-gbp-2 |
| tags: | added: juno-backport-potential |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-2 → kilo-gbp-3 |
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-3 → kilo-gbp-4 |
| status: | In Progress → Fix Committed |
| Changed in group-based-policy: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on group-based-policy (master) | #2 |
To post a comment you must log in.
Fixed by: https:/