Bug 1550925

Summary: virt-manager loses track of VM after 'virt-clone --replace' is used
Product: [Community] Virtualization Tools Reporter: Xiaodai Wang <xiaodwan>
Component: virt-managerAssignee: Pavel Hrdina <phrdina>
Status: CLOSED WORKSFORME QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: berrange, crobinso, gscrivan, juzhou, mxie, mzhan, tburke, tzheng
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-30 00:31:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
virt-manager debug log none

Description Xiaodai Wang 2018-03-02 10:01:10 UTC 
Description of problem:
libvirtError: Domain not found: no domain with matching uuid 'xxxx'

Version-Release number of selected component (if applicable):
virt-manager-1.4.3-3.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Prepare a guest, keep it in shutdown status.
2. Open virt-manager and connect to the connection which has the guest.
3. Clone the guest with "--replace" argument.
# virt-clone -o test --name test -f /var/lib/libvirt/images/e.img  --debug --replace

Actual results:
libvirtError: Domain not found: no domain with matching uuid 'xxxx' displays.

Expected results:
No libvirtError displays and the guest should be opened successfully.

Additional info:
Comment 2 Xiaodai Wang 2018-03-02 10:40:43 UTC 
Created attachment 1402961 [details]
virt-manager debug log
Comment 4 Pavel Hrdina 2019-02-28 13:45:22 UTC 
Moving to upstream, this is corner case where you need to clone guest to the same name, which is almost never done by users, and you need to have virt-manager GUI running.
Comment 5 Cole Robinson 2020-01-30 00:31:24 UTC 
In my testing with current git this doesn't seem to happen, so I guess it's fixed nowadays