Chad Smith

> we could always just make this a deprecation log and deal with this in the same way that we choose to deal with other new deprecations on older series...

I think this is just waiting on two integration test fixes. But, I'd like this in 24.3 as we are introducing a "breaking change" as far as warnings being emitted...

Thanks @holmanb . I've added two supplemental commits to your branch for reviiew - move from LOG.warning to util.deprecate() so we can better prompt any consumers of this feature that...

@holmanb I think I resolved your last pass of review comments. Please take a look and make sure I didn't miss anything.

@holmanb I think we want this #5209 in milestone 24.2 only if #5411 merged because #5491will give us an easy downstream/stable release mechanism to avoid warnings on "new" deprecation messages...

I think now that milestone 24.2 has been released. We can merge this pending your approval @holmanb

> > I think now that milestone 24.2 has been released. We can merge this pending your approval @holmanb > > Thanks @blackboxsw taking one last look at this now,...

Thank you for this correction @dermotbradley. I was basing my suggestion off of adduser behavior as seen in incus/lxd alpine cloud images and assumed it'd be comparable for /usr/bin/passwd ~...

It may be irrelevant due to the timestamp of where the script is called is after cloud-init's failure to rename a device that already exists on the most recent boot,...

The second variable at play here seems to also be the network-manager-fix-ovs-interfaces.py script triggered by the systemd unit with the Description=Service that will assign mac address for the sriov vf...