Thanks for your reply, Robert. I'm puzzled - how could both machines get the same ID? Surely Uyuni issues it to the client during the bootstrap process? Come to that, where is machine_id stored on client and server? I can see that var in /etc/minion but it's commented out. It's also mentioned, but not defined in /etc/salt/minion.d/susemanager.conf (Is this the same as the "Uyuni System Id" as reported by the Webui?) This prompted me to test again, but with disappointing results for these two machines. * On Uyuni: I deleted the 'current' 00015 machine via the WebUI * Upon re-adding Machine1 using bootstrap, it's now allocated ID 1000010048 Great! So let's add Machine2.... Oh now, now that one is allocated ID 1000010048 as well, and Machine1 has disappeared. Argh! I then repeated the above by removing salt-minion and it's config from the Centos clients: yum -y remove salt-minion rm /etc/salt -rf And repeated the above. Again, both machines replace each other on adding. I then introduced a third client, Machine3. This time Centos7, and added that using bootstrap. This worked okay, it added the machine and incremented the Uyuni System Id so I now have 12 machines added. Some progress, and suggesting it's not a wider fault that will affect all new clients added. This is reassuring. However, how do I get both Machine1 and Machine2 added to Uyuni at the same time? And secondary, how might this happen? My thanks S -----Original Message----- From: Robert Paschedag <robert.paschedag@web.de> Sent: 25 September 2020 15:34 To: Simon Avery <Simon.Avery@atass-sports.co.uk> Cc: uyuni-users@opensuse.org Subject: [EXTERNAL EMAIL] Re: [uyuni-users] Uyuni System ID: not incrementing since upgrade. Are your sure, that both machines do NOT have the same machine_id? Robert ⁣sent from my mobile device​ -------- Originale Nachricht -------- Von: Simon Avery <simon.avery@atass-sports.co.uk> Gesendet: Fri Sep 25 15:57:39 GMT+02:00 2020 An: "uyuni-users@opensuse.org" <uyuni-users@opensuse.org> Betreff: [uyuni-users] Uyuni System ID: not incrementing since upgrade. Hello, I have an unusual issue with Uyuni, which I upgraded last Thursday from 2020 07 to 09 using the "Minor" instructions here<:%20https:/www.uyuni-project.org/doc/2020.09/uyuni_upgrade_guide.pdf> The issue I have is that the "Uyuni System ID" is not incrementing after adding a new machine. This is preventing me adding new machines. If I add a new machine (Machine1) using the bootstrap method (Centos 8), it will add the machine correctly and on checking the Details tab, I can see it has Uyuni System ID: 1000010015 It behaves perfectly well and seems correctly registered with Uyuni. I then add another machine (Machine2) using the bootstrap method, which has a different hostname, mac, ip etc. Machine1 has now disappeared from Uyuni's server list. Machine2 is present and correct, but on checking, it is showing Uyuni System ID: 1000010015 So clearly the internal counter is somehow failing to increment and Machine2's details are overwriting Machine1's The previous 10 machines (possibly added before the upgrade) are all present and fine. Please advise, thank you. S

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 <moio@suse.de> 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-registe... HTH Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org

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 <nicola.dimarzo@suse.com> Sent: 28 September 2020 10:42 To: uyuni-users@opensuse.org Subject: Re: [EXTERNAL EMAIL] Re: [uyuni-users] RE: Uyuni System ID: not incrementing since upgrade. Hi Simon, I am not sure if it can help but i have fixed duplicate ID issues in the past following this giude. https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registe... Regards On 28/09/2020 09:09, Simon Avery wrote:

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 <moio@suse.de> 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