Bug 1637554

Summary: [IPv6] Security Group rules dropping IPv6 traffic for any new subnets that are added to the network
Product: Red Hat OpenStack Reporter: Tomas Jamrisko <tjamrisk>
Component: opendaylightAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED ERRATA QA Contact: Noam Manos <nmanos>
Severity: high Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: mariel, mkolesni, nyechiel, sgaddam
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: IPv6
Fixed In Version: opendaylight-8.3.0-7.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-16 17:56:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Jamrisko 2018-10-09 13:23:09 UTC 
Description of problem:
It's possible there is no connectivity between two VMs on different subnets and different computes, as long as the subnets were created after one of the vms was started. 

After talking to Sridhar and Aswin, it seems that it's an sg related issue.



How reproducible:
100%

Steps to Reproduce:
1. Create a network, ipv4 subnet and router
2. Start a VM on this subnet
3. Create an additional ipv6 subnet on the same network and create another network and subnet with ipv6 and ipv4
4. Add these 3 new subnets to the router
5. Start a VM on a different compute
6. Try to reach the new vm from the old one on ipv6

Actual results:
There is no connectivity. Although both vms have ipv6 addresses assigned and connectivity on ipv4 works as expected.
Comment 5 Mike Kolesnik 2018-11-08 13:14:20 UTC 
Retargeted to OSP13 z4 since we want that fix there (will cross tag to OSP 14 as well)
Comment 18 Noam Manos 2018-12-31 13:42:52 UTC 
Since IPv6 is not a supported RFE in ODL OSP13 (it will be OSP15 RFE), changing priority to medium.
Comment 20 errata-xmlrpc 2019-01-16 17:56:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0093