Bug 700552 - blocked on libvirt feaure: vdsm reports Not responding VMs as Up
Summary: blocked on libvirt feaure: vdsm reports Not responding VMs as Up
Keywords:
Status: CLOSED DUPLICATE of bug 701398
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Federico Simoncelli
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On: 701398
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-28 16:20 UTC by David Naori
Modified: 2016-04-18 06:39 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-12 09:36:21 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm log (1.22 MB, application/octet-stream)
2011-04-28 16:20 UTC, David Naori
no flags Details

Description David Naori 2011-04-28 16:20:39 UTC
Created attachment 495585 [details]
vdsm log

Description of problem:
when preforming kill SIGSTOP to a qemu-kvm process and restarting vdsmd, vdsm reports the vm as up.


before vdsmd restart:

vdsClient -s 0 list table
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b  16832  LIBVIRT-NFS-0-03     Up*
vmStats:
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b
        monitorResponse = -1
        statsAge = 149.39

after vdsmd restart:

vdsClient -s 0 list table
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b  16832  LIBVIRT-NFS-0-03     Up
vmStats dose not increase above 2:
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b
        monitorResponse = 0
        statsAge = 1.10

Version-Release number of selected component (if applicable):
vdsm-4.9-60

How reproducible:
100%

Steps to Reproduce:
1.kill -19 qemu-kvm process
2.service vdsmd restart

Comment 2 Dan Kenigsberg 2011-04-29 22:09:24 UTC
Does the state flips back to Up* after a minute? If so, that's not a real bug.

Comment 3 David Naori 2011-04-30 13:25:57 UTC
(In reply to comment #2)
> Does the state flips back to Up* after a minute?

No, statsAge dose not increase above 2- the vm state stays Up after a minute.

Comment 5 Dan Kenigsberg 2011-05-12 09:36:21 UTC
This would be solved by underlying bug 701398.

*** This bug has been marked as a duplicate of bug 701398 ***


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