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

Bug 1131157

Summary: Failed to complete snapshot 'snmpshwithmem' creation for VM 'VM3' for RHEL7 guest over RHEL7 host with ovirt-guest-agent.
Product: Red Hat Enterprise Virtualization Manager Reporter: Nikolai Sednev <nsednev>
Component: ovirt-engineAssignee: Liron Aravot <laravot>
Status: CLOSED WORKSFORME QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acathrow, amureini, ecohen, gklein, iheim, laravot, lpeer, nsednev, ofrenkel, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-03 12:40:49 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 from both hosts
none
logs none

Description Nikolai Sednev 2014-08-18 14:55:18 UTC
Created attachment 927942 [details]
logs from both hosts

Description of problem:
Failed to create a simple snapshot including memory from guest running VM3 with RHEL7 as a guest, over RHEL7 host.

Version-Release number of selected component (if applicable):
vdsm-4.16.1-4.gitb2bf270.el7.x86_64
sanlock-3.1.0-2.el7.x86_64
qemu-kvm-1.5.3-60.el7_0.5.x86_64
libvirt-1.1.1-29.el7_0.1.x86_64
qemu-kvm-common-1.5.3-60.el7_0.5.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Create VM with 1 bootable disk from NFS SD with installed RHEL7 on it and within RHEL7 3.5 HE environment containing one host for HE, while second host should be added to HE from WEBUI not as HA, just as additional host to the host cluster (HA not running on it).
2.Run VM over host that is not running HE and not a part of HA.
3.Try creating snapshot...

Actual results:
Snapshot fails with error " Failed to complete snapshot 'snmpshwithmem' creation for VM 'VM3' "

Expected results:
Snapshot should succeed.

Additional info:
Logs from two hosts provided.

Comment 1 Nikolai Sednev 2014-08-18 15:02:06 UTC
Happens for snapshots with ram or without ram tab selected.

Comment 3 Nikolai Sednev 2014-08-19 10:29:07 UTC
Engin's version is ovirt-engine-setup-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch

Comment 4 Omer Frenkel 2014-08-19 13:50:44 UTC
looks like the createVolume fails:
2014-08-18 17:08:05,473 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler_Worker-59) BaseAsyncTask::LogEndTaskFailure: Task 81351474-0281-429c-ac00-32dc2433524b (Parent Command CreateAllSnapshotsFromVm, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) ended with failure:
-- Result: cleanSuccess
-- Message: VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Error creating a new volume, code = 205,
-- Exception: VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Error creating a new volume, code = 205

Allon, can someone take a look?

Comment 5 Allon Mureinik 2014-08-20 08:32:46 UTC
Liron, can you take a look please?

Comment 7 Liron Aravot 2014-09-02 07:13:47 UTC
Nikolai, the issue here seems to be a failure to write to the leases file on the domain, it's under the dom_md folder (called leases).

can you check it?

Comment 8 Nikolai Sednev 2014-09-02 12:07:48 UTC
(In reply to Liron Aravot from comment #7)
> Nikolai, the issue here seems to be a failure to write to the leases file on
> the domain, it's under the dom_md folder (called leases).
> 
> can you check it?

I think it's connected to newer version of qemu-kvm, which should be different than I used, please check if the provided one is good one. 
Regarding "dom_md", that's a real problem, I don't have the setup anymore, so please reproduce the bug using described scenario on your environment and get the log, I'm sorry to give you such an answer, but don't have the resources for this:(.

Comment 9 Liron Aravot 2014-09-02 12:19:43 UTC
The issue shouldn't be related to qemu-kvm, as the failure is in sanlock.init_resource.

I ran similar scenario on my env and it worked fine, as i don't have access to your storage i can't know what was the underlying issue.

closing this for now on INSUFFICIENT DATA.

Comment 11 Nikolai Sednev 2014-09-02 13:13:01 UTC
Created attachment 933760 [details]
logs

Comment 12 Nikolai Sednev 2014-09-02 14:45:05 UTC
Latest attached files connected to https://bugzilla.redhat.com/show_bug.cgi?id=1132529. Original bug environment have to be established in order to get bug reproduced, on R&D or QE side.

Comment 13 Liron Aravot 2014-09-03 07:56:03 UTC
Nikolai, From the initial testing that we have done the issue hasn't reproduced. If you manage to reproduce it please write it down here. Right now we don't have enough info to continue to that bug. leaving it open for now till it'll be reproduced.

Comment 14 Allon Mureinik 2014-09-03 12:40:49 UTC
bug 1132529 has nothing to do with this bug.

We've tried to reproduce THIS bug on several envs, both in dev and in storage QE, and failed. If you can reproduce it, please do so, attach updated logs, and add exact steps to reproduce.

Comment 15 Nikolai Sednev 2014-09-03 16:42:11 UTC
Worked for me as well on latest components:
vdsm-4.16.2-1.gite8cba75.el7.x86_64
sanlock-3.1.0-2.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7_0.2.x86_64
ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch