Bug 1390991
| Summary: | Wrong error message when executing qemu-img commit with wrong arguments while confusing base and top volumes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ala Hino <ahino> |
| Component: | qemu-kvm-rhev | Assignee: | Hanna Czenczek <hreitz> |
| Status: | CLOSED ERRATA | QA Contact: | Ping Li <pingl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | aliang, chayang, coli, hachen, juzhang, knoel, meyang, michen, mrezanin, ngu, nsoffer, pingl, rbalakri, virt-maint, xuwei |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:37:14 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: | |||
|
Description
Ala Hino
2016-11-02 11:26:20 UTC
Trying to clean up the mess from vdsm - the command run was:
qemu-img commit -b 873a90e2-cc23-4b32-918c-b7d1374c8605 -f raw 481f0c94-3d68-4080-a810-b0e1bd3a29a8
Both file exists - the real chain is (top -> base):
873a90e2-cc23-4b32-918c-b7d1374c8605 -> 481f0c94-3d68-4080-a810-b0e1bd3a29a8
And the error was:
qemu-img: Base 873a90e2-cc23-4b32-918c-b7d1374c8605 not found
I think the error should be that the base image (873a90e2-cc23-4b32-918c-b7d1374c8605) is not in the backing chain of top image (481f0c94-3d68-4080-a810-b0e1bd3a29a8).
Hi, The error message is not wrong, but it is indeed unclear: What it means by “base not found” is “the given base was not found in the backing chain”. I will see to rewrite it to make it more clear. Max Fixed in upstream commit 6b33f3ae8b79726ef0812597b8a83c3e82d31514. Reproduced the issue with below packages:
kernel-3.10.0-514.21.1.el7.x86_64
qemu-kvm-rhev-2.6.0-28.el7_3.9
Test steps:
# qemu-img create -f raw base.img 1G
Formatting 'base.img', fmt=raw size=1073741824
# qemu-img create -f qcow2 sn.qcow2 1G
Formatting 'sn.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
# qemu-img commit -p -t none -b base.img -f raw sn.qcow2
(0.00/100%)
qemu-img: Base 'base.img' not found
Verified the issue with below packages:
kernel-3.10.0-671.el7.x86_64
qemu-kvm-rhev-2.9.0-6.el7
Test steps:
# qemu-img create -f raw base.img 1G
Formatting 'base.img', fmt=raw size=1073741824
# qemu-img create -f qcow2 sn.qcow2 1G
Formatting 'sn.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
# qemu-img commit -p -t none -b base.img -f raw sn.qcow2
(0.00/100%)
qemu-img: Did not find 'base.img' in the backing chain of 'sn.qcow2'
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, 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/RHSA-2017:2392 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, 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/RHSA-2017:2392 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, 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/RHSA-2017:2392 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, 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/RHSA-2017:2392 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, 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/RHSA-2017:2392 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, 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/RHSA-2017:2392 |