Bug 1182774
| Summary: | [RFE][HC] volumes actions should be restricted when volume is assigned as a storage domain within hyperconverged cluster | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Paul Cuzner <pcuzner> | |
| Component: | Frontend.WebAdmin | Assignee: | Gobinda Das <godas> | |
| Status: | CLOSED DUPLICATE | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.5.0 | CC: | bugs, lsurette, Rhev-m-bugs, sabose, sasundar, scohen, srevivo, ykaul | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | FutureFeature | |
| Target Release: | --- | Flags: | sabose:
ovirt-4.3?
rule-engine: planning_ack? sabose: devel_ack+ sasundar: testing_ack+ |
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1183306 (view as bug list) | Environment: | ||
| Last Closed: | 2018-12-10 07:15:28 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: | 1183306 | |||
| Bug Blocks: | 1183307, 1596034 | |||
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. *** Bug 1183306 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 1620198 *** |
Description of problem: In hyperconverged, a gluster volume becomes the storage domain for vm images. However, actions on the volume (stop/remove) are not currently prevented when the volume is actually assigned and in use as a storage domain. Once a volume has been assigned as a storage domain, it should 'own' the glusterfs volume and the workflow around these tasks should change to be rhev orientated. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. in hyperconverged cluster, create a volume and start it 2. add the volume as a storage domain to rhev 3. go to the volumes tab and issue a stop to confirm that a volume action does not link to actions against the associated object in rhev Actual results: stop and remove are allowed underneath an active storage domain. Expected results: For a volume that is a storage domain (hyperconverged - or not!), I would expect the following to happen; * Volume Stop ; - include on the "stop volume" modal dialog the fact that this volume is assigned as a storage domain - once the admin confirms the stop operation, place the domain into maintenance mode for consistency in the UI - once in maintenance mode, the voume stop can be performed * Volume remove (note a stop must have already been performed) - should prompt for confirmation pointing out that the volume is a storage domain - if the user confirms removal - destroy the associated storage domain - issue the vol delete to remove the volume * Volume start; - start the volume - check domain state, and if in maintenance mode issue an activate Additional info: