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

Bug 1145259

Summary:	[RFE] Add option to disconnect hosted-engine NFS storage pool
Product:	[oVirt] ovirt-hosted-engine-ha	Reporter:	Ryan Groten <rgroten>
Component:	RFEs	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED EOL	QA Contact:	Nikolai Sednev <nsednev>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, dfediuck, didi, ecohen, gklein, iheim, istein, lsurette, lveyde, rbalakri, rgroten, sbonazzo, s.kieske, stirabos, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	sla
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-02 11:01:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ryan Groten 2014-09-22 17:01:56 UTC

Description of problem: 
Unable to cleanly unmount the hosted-engine NFS share without affecting all the other running VMs on a host (in v3.4).  When hosted-engine is shutdown and put in global maintenance mode, the hosted-engine storage pool is still mounted and can't be unmounted because the sanlock process is using it.

Additional info:

A hosted-engine --disconnect-storage option could be very useful when performing maintenance.

Comment 1 Doron Fediuck 2014-11-26 09:58:03 UTC

Sandro,
IIRC we have something similar on disconnecting from storage during
installation. Can we unify it?

Comment 2 Sandro Bonazzola 2014-11-26 10:06:32 UTC

I think it's not really useful to unify the disconnection within the command line option and the setup part. In the setup we already have access to the API and to the storage data through the env.
At command line runtime we only have the config files for getting storage info.

Comment 3 Sandro Bonazzola 2015-01-21 16:08:34 UTC

oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 5 Sandro Bonazzola 2015-09-04 09:03:00 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 6 Sandro Bonazzola 2015-10-02 11:01:30 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.