Bug 949293 - vdsm: fail to import a vm with 3 disks and 3 snapshots without collapse because sanlock fails to renue lease and kills vdsm
Summary: vdsm: fail to import a vm with 3 disks and 3 snapshots without collapse becau...
Keywords:
Status: CLOSED DUPLICATE of bug 950003
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Federico Simoncelli
QA Contact: Dafna Ron
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-07 14:29 UTC by Dafna Ron
Modified: 2016-02-10 19:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-01 09:05:01 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
scohen: Triaged+


Attachments (Terms of Use)
logs (1.49 MB, application/x-gzip)
2013-04-07 14:29 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2013-04-07 14:29:17 UTC
Created attachment 732353 [details]
logs

Description of problem:

I imported a vm with 3 disks and 3 snapshots without collapse and the task fails because sanlock fails to renue the lease and kills vdsm 

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

sf13
vdsm-4.10.2-14.0.el6ev.x86_64
sanlock-2.6-2.el6.x86_64
libvirt-lock-sanlock-0.10.2-18.el6_4.3.x86_64
libvirt-0.10.2-18.el6_4.3.x86_64

How reproducible:

100%

Steps to Reproduce:
1. create and export a vm with 3 disks and 3 snapshots
2. remove the vm from the setup
3. import the vm back to the setup without collapse of snapshots
  
Actual results:

we fail to import the vm 

Expected results:

we should be able to import the vm 

Additional info:logs

I added >>> to all the logs before exporting the vm so it will be easy to find it in the logs

Comment 5 Federico Simoncelli 2013-04-29 09:50:42 UTC
In terms of behavior this is a duplicate of bug 950003. If the storage can't sustain the image copy/move and the sanlock timestamp renewal then VDSM is correctly fenced.

Comment 7 Ayal Baron 2013-05-01 09:05:01 UTC
Sanlock is used only for the SPM and the underlying issue is that the storage was not able to sustain the I/O hence this is a dup of bug 950003

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


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