Bug 1459884 - Ipv6PktHandler is not invoked for RS/NS
Summary: Ipv6PktHandler is not invoked for RS/NS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opendaylight
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 12.0 (Pike)
Assignee: Sridhar Gaddam
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-08 12:54 UTC by Sridhar Gaddam
Modified: 2018-10-18 07:20 UTC (History)
6 users (show)

Fixed In Version: opendaylight-6.1.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-12-13 21:31:55 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Sridhar Gaddam 2017-06-08 12:54:11 UTC 
Description of problem:
Ipv6PktHandler is not getting invoked when a VM sends out a RouterSolicitation/NeighborSolicitation request. The packets are punted to the controller as expected, but IPv6PktHandler is not notified.

This is basically a regression following the Singleton changes that were merged in Netvirt.
Comment 1 Nir Yechiel 2017-07-20 09:05:57 UTC 
@Sridhar, the patch seems to be merged. Can you set the fixed-in version?

Thanks,
Nir
Comment 4 Sridhar Gaddam 2017-09-18 03:29:28 UTC 
Steps to verify:

1. Create a Neutron router
2. Create a network with an IPv6 SLAAC subnet.
3. Associate the IPv6 subnet to the neutron router.
4. Spawn a VM on the network. 

Expected Results:
VM should be able to acquire IPv6 address successfully.
Comment 5 Itzik Brown 2017-09-18 11:46:20 UTC 
Checked with opendaylight-6.1.0-2.el7ost.noarch
Comment 9 errata-xmlrpc 2017-12-13 21:31:55 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/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.