Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1459884

Summary:	Ipv6PktHandler is not invoked for RS/NS
Product:	Red Hat OpenStack	Reporter:	Sridhar Gaddam <sgaddam>
Component:	opendaylight	Assignee:	Sridhar Gaddam <sgaddam>
Status:	CLOSED ERRATA	QA Contact:	Itzik Brown <itbrown>
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	lpeer, lruzicka, mkolesni, nyechiel, sgaddam, tvignaud
Target Milestone:	beta	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	opendaylight-6.1.0-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	N/A
Last Closed:	2017-12-13 21:31:55 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 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