yahoo-eng-team team mailing list archive

[OpenStack Infra <1625209@xxxxxxxxxxxxxxxxxx>]

** Changed in: networking-calico
       Status: Invalid => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1625209

Title:
  ipv6 options are being checked for ipv4 subnet

Status in networking-calico:
  In Progress
Status in neutron:
  Invalid

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 Neutron.
  Point of failure: https://github.com/openstack/neutron/blob/7f6b5b5d8953159740f74b0a4a5280527f6baa69/neutron/agent/linux/dhcp.py#L1342
  Traceback: http://paste.openstack.org/show/580996/
  Failure rate: always.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-calico/+bug/1625209/+subscriptions