Bug 2001794
| Summary: | [virt-clone] wrong error message advises to run clone on paused machine | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | smitterl |
| Component: | virt-manager | Assignee: | Jonathon Jongsma <jjongsma> |
| Status: | CLOSED ERRATA | QA Contact: | Hongzhou Liu <hongzliu> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8.5 | CC: | bfu, fjin, jjongsma, jsuchane, juzhou, phrdina, pkrempa, tyan, tzheng, virt-maint |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-3.2.0-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 13:54:55 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: | |||
| Bug Depends On: | 2009080 | ||
| Bug Blocks: | |||
|
Description
smitterl
2021-09-07 08:18:30 UTC
virt-clone is part of the virt-manager package. Fixed upstream by v2.2.1-268-g140a1f3b15d4:
commit 140a1f3b15d47ea5d2d56bdf56d0484419023280
Author: Cole Robinson <crobinso>
Date: Wed Jan 29 16:14:55 2020 -0500
cloner: Drop ability to clone a paused VM
This was fixed in upstream Bug 1725330.
IIUC this will be fixed by the next rebase in 8.6 https://bugzilla.redhat.com/show_bug.cgi?id=2009080 I can reproduce this issue with package: virt-install-2.2.1-4.el8.noarch Steps: 1. Prepare a running status’ vm1 # virsh domstate vm1 >> running 2. Run the command below to clone the VM. # virt-clone --auto-clone --original vm1 --name clone-vm1 >> ERROR Domain with devices to clone must be paused or shutoff. Comment: Since the qcow image has been locked by qemu, a paused vm can not be cloned.This error message needs to be updated 3. Suspend vm1 and clone it # virsh domstate vm1 >> paused # virt-clone --auto-clone --original vm1 --name clone-vm1 >> WARNING Setting the graphics device port to autoport, in order to avoid conflicting. ERROR Couldn't create storage volume 'clone-vm1.img': 'internal error: Child process (/usr/bin/qemu-img convert -f qcow2 -O qcow2 -o compat=1.1,lazy_refcounts /var/lib/libvirt/images/vm1.img /var/lib/libvirt/images/clone-vm1.img) unexpected exit status 1: qemu-img: Could not open '/var/lib/libvirt/images/vm1.img': Failed to get shared "write" lock Is another process using the image [/var/lib/libvirt/images/vm1.img]? ' Then try to verify this bug with new build - virt-install-3.2.0-1.el8.noarch Steps: 1: Prepare a running status’ vm1 # virsh domstate vm1 >> running 2: Run the command below to clone the running VM. # virt-clone --auto-clone --original vm1 --name clone-vm1 >> ERROR Domain to clone must be shutoff. Comment: The error message is clear for the user 3: suspend vm1 and try step 2 again # virsh domstate vm1 >> paused # virt-clone --auto-clone --original vm1 --name clone-vm1 >> ERROR Domain to clone must be shutoff Comment: The error message is clear for the user, failed to clone a paused VM. 4. Shut off vm1 and try step 2 again # virsh domstate vm1 >> shut off # virt-clone --auto-clone --original vm1 --name clone-vm1 >> Allocating 'clone-vm1.img' | 6.0 GB 00:00:00 Clone 'clone-vm1' created successfully. Comment: A shutoff vm can be cloned successfully. Summary - All the test results are as expected. So I moved this bug from ON_QA to VERIFIED status. Hi Sebastian, Because this bug first report on S390, so could you double check the bug? Thanks (In reply to Hongzhou Liu from comment #9) > Hi Sebastian, > > Because this bug first report on S390, so could you double check the bug? > > Thanks I don't think it's necessary. The change is arch-independent and only the error message was changed, IIUC. 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-2022:1862 |