Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Can you please try running the 'qemu-img commit' command under strace -f and
post the output of it? I hope we can see this way what the exact error is.
(In reply to Kevin Wolf from comment #4)
> Can you please try running the 'qemu-img commit' command under strace -f and
> post the output of it? I hope we can see this way what the exact error is.
Hello Kevin,
This bug is not always reproducible,
I am trying get one
Are you sure you attached the log of a failing instance? It ends with this:
12930 write(1, "Image committed.\n", 17) = 17
12930 exit_group(0) = ?
This is the message for successful completion and it has exit code 0, too.
Obviously, the reported output "Error while committing image" and the posted
strace don't match. If the message isn't there in the trace, it can't possibly
have been output.
If we can't get an strace and an observed output that match, I'll have to close
this as INSUFFICIENT_DATA. Any chance we can get more coherent information?
(In reply to Kevin Wolf from comment #13)
> Obviously, the reported output "Error while committing image" and the posted
> strace don't match. If the message isn't there in the trace, it can't
> possibly
> have been output.
>
> If we can't get an strace and an observed output that match, I'll have to
> close
> this as INSUFFICIENT_DATA. Any chance we can get more coherent information?
Hi Kevin,
As the C#8, I have tried run this on a customized autotest env for this bz,
only reproduce this once, and unfortunately the result is uesless on your side.
I believe re-run that script would have same result.
Due to the low reproducibility of this bz, it wont impact a lot, it's fine to close on my side.
Thanks,
Xiaoqing
Description of problem: qemu-img: Error while committing image Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.406.el6.x86_64 qemu-img-0.12.1.2-2.406.el6.x86_64 How reproducible: 2/10 Steps to Reproduce: 1. qemu-img create -f qcow2 /usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/sn1.qcow2 -b /usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/sles11sp3-64-virtio.qcow2 2. /usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/qemu/qemu -monitor stdio \ -S \ -name 'virt-tests-vm1' \ -nodefaults \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20130930-140029-sTvpKEHN,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130930-140029-sTvpKEHN,server,nowait \ -device isa-serial,chardev=serial_id_serial1 \ -chardev socket,id=seabioslog_id_20130930-140029-sTvpKEHN,path=/tmp/seabios-20130930-140029-sTvpKEHN,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20130930-140029-sTvpKEHN,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 \ -drive file='/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/sn1.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,snapshot=off,format=qcow2,aio=native \ -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,bootindex=0 \ -device virtio-net-pci,netdev=idpWdCHL,mac='9a:f7:f8:f9:fa:fb',bus=pci.0,addr=0x3,id='id7Wq546' \ -netdev tap,id=idpWdCHL,vhost=on \ -m 8192 \ -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \ -cpu 'Opteron_G3' \ -M rhel6.5.0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -vga cirrus \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off \ -no-kvm-pit-reinjection \ -enable-kvm 3. shutdown guest, and qemu-img commit /usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/sn1.qcow2 Actual results: Error while committing image echo $? 1 Expected results: committing success Additional info: not stable reproducer