I don't want to revert the original fix because I don't think that gets
us to a better place. With that fix in place, at least deployers have a
chance of seeing from the sanity check that they need to update dnsmasq
to a higher minimum version in order to use stateful IPv6. If they see
it and update dnsmasq, then stateful IPv6 has a chance of working. If we
revert then we have no chance of it working.

Ideally, from a end user's point of view, we'd generate an API error if
the agents aren't going to be able to handle a stateful IPv6 subnet. So,
I think we should work toward that. But, to accomplish that, we'll end
up with a fix that cannot be backported to Newton, right?

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

  dhcp_release6 can be called when it is not present

Status in neutron:
  In Progress
Status in dnsmasq package in Ubuntu:

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An


  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to