Right, neutron DB layer has these fields set for both IPv4 and IPv6
layers, it also adds them when making subnet dict. So other places in
code expect these fields and the reported case might not be single one.
I'd suggest fix this on Calico plugin side.

** Also affects: networking-calico
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: Confirmed => Invalid

** Changed in: neutron
     Assignee: Oleg Bondarev (obondarev) => (unassigned)

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  ipv6 options are being checked for ipv4 subnet

Status in networking-calico:
Status in neutron:

Bug description:
  When DHCP agent tries to set fixed_ips parameter for DHCP port (see 
https://bugs.launchpad.net/networking-calico/+bug/1541490) Neutron checks 
ipv6_address_mode and ipv6_ra_mode options of subnet that corresponds to the 
given fixed IP even for IPv4 subnet. And this fails as IPv4 subnet does not 
have such options (see traceback http://paste.openstack.org/show/580996/). And, 
of course, you cannot set such flags for IPv4 subnet.
  I'd expect that such check is performed for IPv6 subnets only.

  Probably, this situation is possible not only while using non-native
  DHCP agent.

  Neutron version: Newton (7f6b5b5d8953159740f74b0a4a5280527f6baa69).
  Environment: Calico (https://github.com/openstack/networking-calico) over 
  Point of failure: 
  Traceback: http://paste.openstack.org/show/580996/
  Failure rate: always.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to