[uyuni-users] VMware cloned VM's are treated as one system in Uyuni
I have a VMware CentOS7 VM which was cloned from another. When I import the first as a Salt client everything is fine. When I go to register the second, a new salt key is generated for the second hostname but when the key is accepted, some attributes of the original registered machine are replaced by the second. In other words, a second registered system is not created, the first system is converted into the identity of the second. The UUID in Uyuni is NOT changed to the hardware uuid of the second machine; The system name IS changed to the second machine; The hostname and ip address remains set as the first machine. UUIDs in the individual VM .vmx files are different Hardware uuids revealed by dmidecode for each VM are different ifcfg scripts on each VM contain unique uuids for the network interfaces IPv6 address for each system are different I've recovered all the salt grains.items by registering each server separately and there is no duplication of any grain value I can find. In short the systems appear to be unique but Uyuni thinks they are the same. Interestingly both systems were originally registered separately without this problem in Spacewalk version 28 Any ideas as to what to look for next?! T *Please note I am not normally in the office on Mondays or Fridays* ___________________________________________________________ TIM SHAW - Deputy Director - Network Services Medical Sciences Division - University of Oxford email : tim.shaw@medsci.ox.ac.uk tel : +44 (0)1865 289480 -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Apologies for my failure to RTFM This is indeed documented in https://www.uyuni-project.org/uyuni-docs/uyuni/administration/tshoot-registe... Thanks for the pointers Nicola and Tobias! T
"Tim Shaw" <Tim.Shaw@medsci.ox.ac.uk> 31/03/2020 12:02 >>> I have a VMware CentOS7 VM which was cloned from another. When I import the first as a Salt client everything is fine. When I go to register the second, a new salt key is generated for the second hostname but when the key is accepted, some attributes of the original registered machine are replaced by the second. In other words, a second registered system is not created, the first system is converted into the identity of the second.
The UUID in Uyuni is NOT changed to the hardware uuid of the second machine; The system name IS changed to the second machine; The hostname and ip address remains set as the first machine. UUIDs in the individual VM .vmx files are different Hardware uuids revealed by dmidecode for each VM are different ifcfg scripts on each VM contain unique uuids for the network interfaces IPv6 address for each system are different I've recovered all the salt grains.items by registering each server separately and there is no duplication of any grain value I can find. In short the systems appear to be unique but Uyuni thinks they are the same. Interestingly both systems were originally registered separately without this problem in Spacewalk version 28 Any ideas as to what to look for next?! T *Please note I am not normally in the office on Mondays or Fridays* ___________________________________________________________ TIM SHAW ‑ Deputy Director ‑ Network Services Medical Sciences Division ‑ University of Oxford email : tim.shaw@medsci.ox.ac.uk tel : +44 (0)1865 289480 ‑‑ To unsubscribe, e‑mail: uyuni‑users+unsubscribe@opensuse.org To contact the owner, e‑mail: uyuni‑users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
participants (1)
-
Tim Shaw