RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2038040 - Clone a guest with sysinfo uuid failed
Summary: Clone a guest with sysinfo uuid failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-manager
Version: 9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Jonathon Jongsma
QA Contact: Hongzhou Liu
URL:
Whiteboard:
Depends On: 2135791
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-07 07:22 UTC by Lili Zhu
Modified: 2023-05-09 08:44 UTC (History)
9 users (show)

Fixed In Version: virt-manager-4.1.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:39:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-107055 0 None None None 2022-01-07 07:24:22 UTC
Red Hat Product Errata RHBA-2023:2255 0 None None None 2023-05-09 07:39:31 UTC

Description Lili Zhu 2022-01-07 07:22:00 UTC 
Description of problem:
Clone a guest with sysinfo uuid failed


Version-Release number of selected component (if applicable):
virt-install-3.2.0-11.el9.noarch
libvirt-7.10.0-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.define a guest with the following xml snippet
# virsh dumpxml avocado-vt-vm1
<domain type='kvm'>
  <name>avocado-vt-vm1</name>
  <uuid>80d5908b-4402-4a91-8465-6e3f16541215</uuid>
...
  <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>80d5908b-4402-4a91-8465-6e3f16541215</entry>
    </system>
  </sysinfo>
...

2. clone the guest
# virt-clone -o avocado-vt-vm1 -n clone --auto-clone
ERROR    UUID mismatch between <uuid> and <sysinfo>


Actual results:
Cloning failed


Expected results:
Cloning succeed

Additional info:
If I define a guest whose UUID mismatch between <uuid> and <sysinfo>, then it will report the same error
# virsh define avocado-vt-vm1.xml 
error: Failed to define domain from avocado-vt-vm1.xml
error: UUID mismatch between <uuid> and <sysinfo>

I guess when clone the guest, it will generate a new uuid for the new guest, but this new uuid will not be applied to the sysinfo uuid. sysinfo uuid in new guest remains the same with the one in orginal guest. Then libvirt will report the above error. Please help to check.
Comment 1 Jaroslav Suchanek 2022-01-28 15:40:23 UTC 
virt-clone would need to adjust the uuid element of sysinfo too.
Comment 2 Cole Robinson 2022-08-21 20:23:40 UTC 
Thanks for the report. This is fixed upstream now:

commit b0d0516736320315a70f74aff3759fb35dd35d9d (HEAD -> main)
Author: Cole Robinson <crobinso>
Date:   Sun Aug 21 16:21:10 2022 -0400

    cloner: Sync <uuid> and <sysinfo> system uuid
Comment 3 John Ferlan 2022-08-22 10:52:23 UTC 
Jonathon - for when you do the next virt-manager rebase.
Comment 4 Hongzhou Liu 2022-11-20 16:06:19 UTC 
Pre-verify this bug with:
libvirt-8.9.0-2.el9.x86_64
virt-install-4.1.0-1.el9.noarch

Step 1: 
1.define a guest with the following xml snippet
# virsh dumpxml rhel9
<domain type='kvm'>
  <name>rhel9</name>
  <uuid>be2137b2-e265-4102-897f-0320a829a55a</uuid>
...
  <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>be2137b2-e265-4102-897f-0320a829a55a</entry>
    </system>
  </sysinfo>
...

2. clone the guest
# virt-clone -o rhel9 -n rhel9-clone --auto-clone
Allocating 'rhel9-5-clone-1.qcow2'                                                                                          | 1.6 GB  00:00:12 ... 
Clone 'rhel9-clone' created successfully.

Test result, guest can be cloned successfully

Based on this, I add verified:tested flag, Thanks
Comment 7 Hongzhou Liu 2023-01-11 02:26:11 UTC 
Verify this bug on latest RHEL9.2

packages:
virt-install-4.1.0-2.el9.noarch
libvirt-8.10.0-2.el9.x86_64
qemu-kvm-7.2.0-3.el9.x86_64

Step 1: 
1.define a guest with the following xml snippet
# virsh dumpxml rhel9u2
<domain type='kvm'>
  <name>rhel9u2</name>
  <uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>
...
 <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
    </system>
  </sysinfo>

...

2. clone the guest
# virt-clone -o rhel9u2 -n rhel9-clone --auto-clone
Allocating 'rhel9-clone.qcow2'                                                                                              | 1.7 GB  00:00:17 ... 

Clone 'rhel9-clone' created successfully.

3: check the xml for rhel9-clone:

<domain type='kvm'>
  <name>rhel9u2</name>
  <uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>

...

  <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
    </system>
  </sysinfo>
...

Test result, guest can be cloned successfully and the uuid for clone guest is the same with origin guest.

Based on this, I change the status to VERIFIED, Thanks
Comment 8 Hongzhou Liu 2023-01-11 15:16:08 UTC 
Correct my verify steps,

1.define a guest with the following xml snippet
# virsh dumpxml rhel9u2
<domain type='kvm'>
  <name>rhel9u2</name>
  <uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>
...
 <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
    </system>
  </sysinfo>

...

2. clone the guest
# virt-clone -o rhel9u2 -n rhel9-clone --auto-clone
Allocating 'rhel9-clone.qcow2'                                                                                              | 1.7 GB  00:00:17 ... 

Clone 'rhel9-clone' created successfully.

3: check the xml for rhel9-clone:

<domain type='kvm'>
  <name>rhel9-clone</name>
  <uuid>dba4bc4e-1b19-4024-99ac-3b9664ab66c0</uuid>

...

  <sysinfo type='smbios'>
    <system>
      <entry name='uuid'>dba4bc4e-1b19-4024-99ac-3b9664ab66c0</entry>
    </system>
  </sysinfo>
...

Test result, guest can be cloned successfully.(virt-clone will generate a new uuid for clone guest)


Based on this, I change the status to VERIFIED, Thanks
Comment 10 errata-xmlrpc 2023-05-09 07:39:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (virt-manager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2255
Note You need to log in before you can comment on or make changes to this bug.