> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known
Looking at the upstream commit description, isn't it just that a DHCPv6 lease expires and the server NAKs a request for the same IP again? Or is that not sufficient to trigger the problem.
In any case, I appreciate there might be difficulty in testing the fix, but what's the actual criteria you propose to use to decide when the bug is to be marked verification-done-bionic?
> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known
Looking at the upstream commit description, isn't it just that a DHCPv6 lease expires and the server NAKs a request for the same IP again? Or is that not sufficient to trigger the problem.
In any case, I appreciate there might be difficulty in testing the fix, but what's the actual criteria you propose to use to decide when the bug is to be marked verification- done-bionic?