I just updated to main-n261544-cee09bda03c8 based (via source) and now /etc/machine-id and /var/db/machine-id disagree ; more

# cat /etc/hostid /etc/machine-id /var/db/machine-id
a4f7fbeb-f668-11de-b280-ebb65474e619
a4f7fbebf66811deb280ebb65474e619
7227cd89727a462186e3ba680d0ee142

(I'll not be keeping these values for the example system.)

# ls -Tld /etc/hostid /etc/machine-id /var/db/machine-id
-rw-r--r--  1 root  wheel  37 Dec 31 16:00:18 2009 /etc/hostid
-rw-r--r--  1 root  wheel  33 Mar 16 15:16:18 2023 /etc/machine-id
-r--r--r--  1 root  wheel  33 Mar  3 23:03:25 2023 /var/db/machine-id

I observed the delete-old-files deleting
/etc/machine-id during the upgrade. It did
nothing with /var/db/machine-id .

Also, modern hostid generation was switched to
random to avoid an exposure. But the update kept
the old hostid and propogated it (not "-"s) into
/etc/machine-id . So /etc/machine-id now has the
same exposure.

Later I'll see if stable/13 also got such behavior
for its upgrade.

I've not been dealing with releng/13.2 but upgrades
from releng/13.1 and before likely have the same
questions for what the handling should be vs. what it
might actually be. Different ways of upgrading might
not be in agreement, for all I know.

===
Mark Millard
marklmi at yahoo.com