This looks a lot like bug 1738998; there's a lot of non-compliant DHCP servers that are unable to deal with using a unique identified for Client Identifier, or pre-existing configuration that has yet to be updated.
The relevant RFC is 4361 [1]; it is meant to address the issues of replacing network hardware leading to losing a lease and any related configuration.
This looks a lot like bug 1738998; there's a lot of non-compliant DHCP servers that are unable to deal with using a unique identified for Client Identifier, or pre-existing configuration that has yet to be updated.
The relevant RFC is 4361 [1]; it is meant to address the issues of replacing network hardware leading to losing a lease and any related configuration.
[1] https:/ /www.rfc- editor. org/rfc/ rfc4361. txt