Comment 71 for bug 1770082

Just confirmed the regression... It's working as expected on boot, but is renaming to the "ID" key, instead of the "set-name" when live.
E.g. if we have:
ens0p3:
    match:
        macaddress: 01:02:03:04:05:06
    set-name: eth0
It will be renamed to ens0p3 on netplan apply.
eth0:
    match:
        macaddress: 01:02:03:04:05:06
    set-name: ens0p3
It will be renamed to eth0...

So basically, on boot it picks up "set-name", and afterwards it picks the ID. If you keep both equal, no problem, but if have different "ID" and "set-name"...