Bug 1151043

Summary: qemu-img shows error message for backing file twice
Product: Red Hat Enterprise Linux 7 Reporter: Ademar Reis <areis>
Component: qemu-kvm-rhevAssignee: Hanna Czenczek <hreitz>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: areis, dyuan, hhuang, juzhang, juzhou, kwolf, mazhang, mbooth, mrezanin, mzhan, ptoscano, rjones, tzheng, virt-bugs, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: V2V
Fixed In Version: 2.3.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1140946
: 1238639 (view as bug list) Environment:
Last Closed: 2015-12-04 16:18:59 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: 1140946    
Bug Blocks: 1238639    

Comment 3 Hanna Czenczek 2015-06-10 15:19:27 UTC
This bug seems to have been fixed by the RHEV rebase to 2.3. Should there be a BZ for qemu-kvm?

Max

Comment 4 Ademar Reis 2015-06-10 19:00:29 UTC
(In reply to Max Reitz from comment #3)
> This bug seems to have been fixed by the RHEV rebase to 2.3. Should there be
> a BZ for qemu-kvm?

This is a minor bug and there's a workaround in libvirtfs already. I woudn't bother, having it fixed upstream and in -rhev is enough.

Comment 5 mazhang 2015-07-01 02:04:24 UTC
Reproduce this bug on qemu-img-rhev-2.1.2-16.el7.x86_64.

Steps:
# qemu-img create -f qcow2 -b /tmp/nosuchfile /tmp/overlay
qemu-img: /tmp/overlay: Could not open '/tmp/nosuchfile': Could not open '/tmp/nosuchfile': No such file or directory: No such file or directory


Verify this bug on qemu-img-rhev-2.3.0-2.el7.x86_64.

Result:
# qemu-img create -f qcow2 -b /tmp/nosuchfile /tmp/overlay
qemu-img: /tmp/overlay: Could not open '/tmp/nosuchfile': No such file or directory

This bug has been fixed.

Comment 7 errata-xmlrpc 2015-12-04 16:18:59 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, 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://rhn.redhat.com/errata/RHBA-2015-2546.html