Bug 1145259 - [RFE] Add option to disconnect hosted-engine NFS storage pool
Summary: [RFE] Add option to disconnect hosted-engine NFS storage pool
Keywords:
Status: CLOSED EOL
Alias: None
Product: ovirt-hosted-engine-ha
Classification: oVirt
Component: RFEs
Version: ---
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Doron Fediuck
QA Contact: Nikolai Sednev
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 17:01 UTC by Ryan Groten
Modified: 2022-03-16 08:58 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-02 11:01:30 UTC
oVirt Team: SLA
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45329 0 None None None 2022-03-16 08:58:35 UTC

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.


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