[OVSDB-277] Address exceptions when SG remote_group_id has both IPv4 and IPv6 addresses Created: 28/Jan/16 Updated: 02/Feb/16 Resolved: 02/Feb/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | openstack.net-virt-providers |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sridhar Gaddam | Assignee: | Sridhar Gaddam |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5134 |
| Priority: | High |
| Description |
|
When a deployment has a combination of IPv4/v6 addresses and a SecurityGroup rule is configured with remote_group_id, OVSDB should consider the IPv4 or IPv6 addresses from the remote_group based on the Security Group EtherType. |
| Comments |
| Comment by Sridhar Gaddam [ 28/Jan/16 ] |
|
Proposed a fix as part of the following patch - https://git.opendaylight.org/gerrit/#/c/33717/ |
| Comment by Sam Hague [ 31/Jan/16 ] |
|
https://git.opendaylight.org/gerrit/#/c/33717/ |
| Comment by Sam Hague [ 02/Feb/16 ] |
|
Sridhar, does the patch you submitted fix this bug? |
| Comment by Sridhar Gaddam [ 02/Feb/16 ] |
|
Yes Sam. It fixes the issue, we can close this bug. |