Public bug reported:
When an ipv6 auto_address subnet is added to an existing network with IPv4
subnet, the dhcp port in the network is simply updated with an IPv6 address.
However, neutron does not send any port_update notification for the dhcp
port. This causes inconsistencies (while configuring anti-spoofing rules)
for external controllers (like OpenDaylight) as the dhcp port info
in controller does not match with the dhcp port info in Neutron db.
** Affects: neutron
Importance: Undecided
Assignee: Sridhar Gaddam (sridhargaddam)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Sridhar Gaddam (sridhargaddam)
** Changed in: neutron
Status: New => In Progress
** Summary changed:
- Port update notification not sent when an IPv6 auto_address subnet is created
on an existing IPv4 network.
+ DHCP Port update notification not sent when an IPv6 auto_address subnet is
created on an existing IPv4 network.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1536998
Title:
DHCP Port update notification not sent when an IPv6 auto_address
subnet is created on an existing IPv4 network.
Status in neutron:
In Progress
Bug description:
When an ipv6 auto_address subnet is added to an existing network with IPv4
subnet, the dhcp port in the network is simply updated with an IPv6 address.
However, neutron does not send any port_update notification for the dhcp
port. This causes inconsistencies (while configuring anti-spoofing rules)
for external controllers (like OpenDaylight) as the dhcp port info
in controller does not match with the dhcp port info in Neutron db.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536998/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
