[ovirt-users] Can HA Agent control NFS Mount?

[Martin Sivak]

Hi,

> One by directly using rem_lockspace (since it's the hosted-engine one)

The hosted engine lockspace protects the ID of the node. Global maintenance only disables the state machine, but it still reports data to the shared storage. The hosted engine lock can only be released when the agent is down. If the lock is still there even after you call service ovirt-ha-agent stop, then it is a bug somewhere.

> the other one by stopMonitoringDomain

Shouldn't this be done by VDSM or sanlock when the VM disappears? The lock has to stay acquired any time the VM is running (independently on the hosted engine services or vdsm) to protect the VM's data. We can't release a lock for running VM, because some other host might try to start it and corrupt data by doing it.

Martin

--
Martin Sivák
msivak at redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ


----- Original Message -----
> ----- Original Message -----
> > From: "Bob Doolittle" <bob at doolittle.us.com>
> > To: "Doron Fediuck" <dfediuck at redhat.com>, "Andrew Lau"
> > <andrew at andrewklau.com>
> > Cc: "users" <users at ovirt.org>, "Federico Simoncelli" <fsimonce at redhat.com>
> > Sent: Saturday, June 14, 2014 1:29:54 AM
> > Subject: Re: [ovirt-users] Can HA Agent control NFS Mount?
> >
> > 
> > But there may be more going on. Even if I stop vdsmd, the HA services,
> > and libvirtd, and sleep 60 seconds, I still see a lock held on the
> > Engine VM storage:
> > 
> > daemon 6f3af037-d05e-4ad8-a53c-61627e0c2464.xion2.smar
> > p -1 helper
> > p -1 listener
> > p -1 status
> > s
> > 003510e8-966a-47e6-a5eb-3b5c8a6070a9:1:/rhev/data-center/mnt/xion2.smartcity.net\:_export_VM__NewDataDomain/003510e8-966a-47e6-a5eb-3b5c8a6070a9/dom_md/ids:0
> > s
> > hosted-engine:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/ha_agent/hosted-engine.lockspace:0
> 
> This output shows that the lockspaces are still acquired. When you put
> hosted-engine
> in maintenance they must be released.
> One by directly using rem_lockspace (since it's the hosted-engine one) and
> the other
> one by stopMonitoringDomain.
> 
> I quickly looked at the ovirt-hosted-engine* projects and I haven't found
> anything
> related to that.
> 
> --
> Federico
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>