[Yahoo-eng-team] [Bug 1625209] Re: ipv6 options are being checked for ipv4 subnet
** 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 -- 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
[Yahoo-eng-team] [Bug 1625209] Re: ipv6 options are being checked for ipv4 subnet
If I understand correctly, this is not an independent bug. Rather, it only arises when changes are made in networking-calico to address another bug (1541490). And the only proposed change for _this_ bug is now also in networking-calico. Therefore it doesn't make sense for this bug to have an independent existence from 1541490, or for any changes for this bug to be separated from proposed changes from 1541490. I will close this bug for networking-calico, and ask that you simply combine all of the networking-calico changes that you think are needed for 1541490. ** Changed in: networking-calico Status: In Progress => Invalid -- 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: Invalid 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 -- 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
[Yahoo-eng-team] [Bug 1625209] Re: ipv6 options are being checked for ipv4 subnet
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. https://bugs.launchpad.net/bugs/1625209 Title: ipv6 options are being checked for ipv4 subnet Status in networking-calico: New 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 -- 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
