Miguel Duarte Barroso

> Updated PR / commit message Thanks, it is now easier to understand.

> AFAIU, this would work, according to [DHCP's RFC section 3.2](https://datatracker.ietf.org/doc/html/rfc2131#section-3.2), step 3: > > > If the client receives a DHCPNAK message, it cannot reuse its > > remembered...

> > For transparency, I have to say I skipped ahead too much and focused on migrations :) That's too ambitious. > > oh interesting. no that's a completely valid...

> > > For transparency, I have to say I skipped ahead too much and focused on migrations :) That's too ambitious. > > > > > > oh interesting....

/remove-lifecycle stale

I currently don't have time to address this issue, independently of how valuable it might be. Not exactly sure when I can get back to this - un-assigning myself.

@davidvossel I think the proposed fix makes sense, and works. But I also think we should somehow test this ... The tricky thing is triggering this condition depends on the...

[This forced push](https://github.com/k8snetworkplumbingwg/multus-cni/compare/24340982a473655141a01c20aa36e745595f643f..f99f08ef3ea53f7eafa2d1eaf6c6e5e0c0d5e8a3) features: - removed the status condition updates - fixed revive's comments (causing the unit test jobs to fail).

@s1061123 I think the approach you shared offline is in line w/ this commit: https://github.com/k8snetworkplumbingwg/multus-cni/pull/777/commits/df801b2e92860769fe18b2b429bf33d1ec995a82 I would appreciate if you'd help me understand how to build the missing data on...

This is being implemented in https://github.com/maiqueb/multus-dynamic-networks-controller/, now that a 3rd party controller with access to the multus thick-plugin socket can trigger delegate add / delete.