Bug 1182784

Summary: [RFE][HC] - a more integrated workflow is needed when removing a storage domain in hyperconverged cluster (Guide me)
Product: [oVirt] ovirt-engine Reporter: Paul Cuzner <pcuzner>
Component: Frontend.WebAdminAssignee: Kaustav Majumder <kmajumde>
Status: CLOSED WONTFIX QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: bugs, knarra, lsurette, Rhev-m-bugs, sabose, srevivo, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: rule-engine: ovirt-4.4?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1183307 (view as bug list) Environment:
Last Closed: 2019-07-19 06:59:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1183307    
Bug Blocks: 1596034    

Description Paul Cuzner 2015-01-15 22:02:04 UTC 
Description of problem:
The virt admin will manage the environment based on high level virt objects in the UI first - i.e. a storage domain. When releasing a storage domain, the workflow is not 'linked' between handling the removal of the rhev object and the glusterfs volume.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Removing a storage domain in a hyperconverged use case should have a workflow similar to the following;

1. admin moves SD to maintenance
2. With the Sd detached, the admin opens the storage tab, selects the domain to remove and chooses "destroy"
3. if the SD was glusterfs domain the "Destroy storage domain" modal dialog should include an option to stop and delete the underlying glusterfs volume
4. if the option to remove the gluster volume is checked a further check box to purge any data from the volume should be provided


Additional info:
Comment 1 Yaniv Lavi 2015-04-20 11:36:07 UTC 
This should be done via guide me for removal in HC use case.
Comment 2 Red Hat Bugzilla Rules Engine 2015-12-01 15:35:30 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 3 Yaniv Lavi 2016-03-08 13:25:41 UTC 
*** Bug 1183307 has been marked as a duplicate of this bug. ***
Comment 5 Sahina Bose 2019-07-19 06:59:26 UTC 
We have implemented linking of gluster volume to storage domain that already addresses this.
Guide me is not planned for now. Hence closing this