Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 949293

Summary: vdsm: fail to import a vm with 3 disks and 3 snapshots without collapse because sanlock fails to renue lease and kills vdsm
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: vdsmAssignee: Federico Simoncelli <fsimonce>
Status: CLOSED DUPLICATE QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: abaron, amureini, bazulay, hateya, iheim, lpeer, scohen, ykaul
Target Milestone: ---Flags: scohen: Triaged+
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-01 09:05:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

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 ***