Bug 701107 - VDSM: guest with CD attached on boot will cause 'Stats function failed' error if disabling ISO during migration
Summary: VDSM: guest with CD attached on boot will cause 'Stats function failed' error...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Federico Simoncelli
QA Contact: Dafna Ron
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-01 08:30 UTC by Dafna Ron
Modified: 2011-12-06 07:15 UTC (History)
6 users (show)

Fixed In Version: vdsm-4.9-66
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:15:27 UTC
Target Upstream Version:


Attachments (Terms of Use)
logs (2.01 MB, application/x-gzip)
2011-05-01 08:30 UTC, Dafna Ron
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description Dafna Ron 2011-05-01 08:30:52 UTC
Created attachment 496032 [details]
logs

Description of problem:

disabling ido domain during guest migration will cause the below error

Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at 
0x1a7ca08>


Version-Release number of selected component (if applicable):
ic114

root@blond-vdsg vdsm]# rpm -qa |grep vdsm
vdsm-4.9-63.el6.x86_64
vdsm-debug-plugin-4.9-63.el6.x86_64
vdsm-cli-4.9-63.el6.x86_64
vdsm-debuginfo-4.9-63.el6.x86_64
[root@blond-vdsg vdsm]# rpm -qa |grep libvirt
libvirt-0.8.7-18.el6.x86_64
libvirt-client-0.8.7-18.el6.x86_64
libvirt-python-0.8.7-18.el6.x86_64
libvirt-debuginfo-0.8.7-18.el6.x86_64
libvirt-devel-0.8.7-18.el6.x86_64
[root@blond-vdsg vdsm]# rpm -qa |grep qemu
gpxe-roms-qemu-0.9.7-6.7.el6.noarch
qemu-kvm-0.12.1.2-2.152.el6.x86_64
qemu-img-0.12.1.2-2.152.el6.x86_64


How reproducible:

100%

Steps to Reproduce:
1. create guest with cd attached in boot 
2. run VM 
3. migrate VM
4. put ISO domain in maintenance while VM is migrating

Actual results:

we will get an error from vdsm:

Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at 
0x1a7ca08>


Expected results:

deactivating ISO domain should have no effect in rhev

Additional info:logs

Comment 1 Dafna Ron 2011-05-01 08:39:13 UTC
to add user experience:
I tested on 3 VM's: 1 migrated with no errors, one was put in pause and I tried to start it became non-responsive and the third failed migration

Comment 2 Dan Kenigsberg 2011-05-01 19:09:55 UTC
Note that the source shows all kinds of errors, due to bug 701106.

Federico, any idea why vdsm/utils:526 does not log any backtrace?

Comment 3 Federico Simoncelli 2011-05-04 14:05:46 UTC
Dan, I suppose the problem is in the SimpleLogAdapter (logUtils.py:5).
The backtrace is back if in vdsm/vm.py:492 you comment out:

self.log = SimpleLogAdapter(self.log, {"vmId" : self.conf['vmId']})

Comment 4 Dan Kenigsberg 2011-05-13 08:45:01 UTC
Dafna, please reproduce this with the next vdsm build, where we added useful logging.

Comment 5 Dan Kenigsberg 2011-05-15 07:38:16 UTC
On Sun, May 15, 2011 at 09:58:53AM +0300, Dafna Ron wrote:
> can you put this on_QA + build?
> I just have a lot of bugs so I don't want this to fall between the cracks.

Done, thanks.

Comment 6 Dafna Ron 2011-05-18 16:35:32 UTC
verified on vdsm-4.9-67.el6.x86_64


error is:

Thread-21302::ERROR::2011-05-18 19:29:55,929::guestIF::300::vm.Vm::(run) vmId=`55e2084c-e9de-489e-991d-eb402b7b5f2f`::Unexpected exception: Traceback (most recent call last):
4c815194-f3e2-4572-ba77-d69b68d99ede::ERROR::2011-05-18 19:30:00,141::vm::1541::vm.Vm::(cont) vmId=`55e2084c-e9de-489e-991d-eb402b7b5f2f`::cannot cont while Down

Comment 7 errata-xmlrpc 2011-12-06 07:15:27 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.

http://rhn.redhat.com/errata/RHEA-2011-1782.html


Note You need to log in before you can comment on or make changes to this bug.