Thanks, Nicola.
My issue is now resolved - in a slightly simpler way. On affected machines;
rm /etc/machine-id
systemd-machine-id-setup
Then bootstrap to Uyuni and all is well. My problematic machines are co-existing and additional ones added.
I've also now gathered the values of this file for the 200+ centos machines I help manage and found another 13 machines sharing the same values (which have not yet migrated to Uyuni) and fixed those.
A classic example of a lurking problem that's ignored until something decided it was useful.
Regards
Simon
-----Original Message-----
From: Nicola Di Marzo
Hi Silvio
Thanks for this - this does indeed look to be the core of the issue;
machine1# cat /etc/machine-id 57dcc3a1bbed44f6a97dc4c8058eb4d3
machine2# cat /etc/machine-id 57dcc3a1bbed44f6a97dc4c8058eb4d3
I don't know the history of these machines, but cloning does seem possible. Both machine co-existed on Spacewalk okay, but of course they used osad and rhnsd which presumably don't care about this value.
Thanks to you and Robert for your help - I think I'm good to take it on from here.
Regards
S
-----Original Message----- From: Silvio Moioli
Sent: 28 September 2020 08:34 To: uyuni-users@opensuse.org Subject: [EXTERNAL EMAIL] Re: [uyuni-users] RE: Uyuni System ID: not incrementing since upgrade. On 28/09/2020 09.27, Simon Avery wrote:
I'm puzzled - how could both machines get the same ID? Surely Uyuni issues it to the client during the bootstrap process? The machine-id is a unique identifier that comes either from hardware, or from your virtualization software, or in worst case randomly generated - but it should really be unique.
Uyuni does _not_ set it, rather it uses it to determine if a client is the same of another that's already registered or not (despite possible changes in hostname, IP addresses and so on).
Note that the machine-id is very different from the minion key, or the name that you see in the Uyuni Web UI!
You can learn more about machine-id here:
https://www.man7.org/linux/man-pages/man5/machine-id.5.html
It is a requirement that any Uyuni client has a unique and fixed machine-id. Note that if you clone VMs the machine-id might be cloned as well, so you need to change it.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-r egisterclones.html
HTH
Regards, -- Silvio Moioli SUSE Manager Development Team
-- Kind Regards, Nicola Di Marzo SUSE Premium Engineer nicola.dimarzo@suse.com +44 7973 975049 -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org