+++ This bug was initially created as a clone of Bug #1182784 +++
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 oVirt object and the glusterfs volume.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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
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.
Isn't this a duplicate of Bug 1182784?
Y(In reply to Sahina Bose from comment #2)
> Isn't this a duplicate of Bug 1182784?
*** This bug has been marked as a duplicate of bug 1182784 ***