i did a mistake in the paste [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker root@kind-1:/# cat /etc/machine-id *24bfea9624e44e01a3859eb6c9ef1dad* root@kind-1:/# hostname *kind-1.17.0-worker*
[root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane root@kind-1:/# cat /etc/machine-id *71ebb3fc051a48b2b45345b67bb1002b* root@kind-1:/# hostname *kind-1.17.0-control-plane* i am trying other approach as well, i might use old libvirt or something, if more info is needed, please let me know, thanks On Thu, Mar 26, 2020 at 5:31 PM Daniel P. Berrangé <berra...@redhat.com> wrote: > On Thu, Mar 26, 2020 at 05:25:59PM +0200, Or Shoval wrote: > > Hi Daniel, > > thanks for the quick reply > > > > we did try to override SMBIOS > > host_uuid_source = "machine-id" > > > > and it didn't work even that nodes have different > > > > [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker > > root@kind-1:/# cat /etc/machine-id > > > > This machine-id really shouldn't be empty - this may well cause issues > in libvirt. > > > [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane > > root@kind-1:/# cat /etc/machine-id > > 71ebb3fc051a48b2b45345b67bb1002b > > You can check what UUID libvirtd thinks it has using: > > $ virsh capabilities |xmllint --xpath /capabilities/host/uuid - > > If the UUIDs reported are different and you still get the > migration error, then it is the duplicate hostname that is > the problem. > > > Regards, > Daniel > -- > |: https://berrange.com -o- > https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- > https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- > https://www.instagram.com/dberrange :| > >
