Bug 1127781
Summary: | A warning is required when moving/copying a disk from a file domain to a block domain | |||
---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Idan Shaby <ishaby> | |
Component: | ovirt-engine-core | Assignee: | Idan Shaby <ishaby> | |
Status: | CLOSED WONTFIX | QA Contact: | Aharon Canan <acanan> | |
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | 3.5 | CC: | acanan, amureini, bugs, derez, ecohen, gklein, iheim, juan.hernandez, ogofen, rbalakri, scohen, tnisan, yeylon | |
Target Milestone: | m1 | Flags: | scohen:
needinfo+
|
|
Target Release: | 3.6.0 | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | storage | |||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 1122510 | |||
: | 1141770 (view as bug list) | Environment: | ||
Last Closed: | 2015-07-07 13:40:49 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1141770, 1141774 |
Description
Idan Shaby
2014-08-07 14:32:44 UTC
This requires quite a bit of grunt-work, pushing out to oVirt 3.5.1 After discussing about it with Allon, Tal and Daniel, we see three different solutions: 1. Add a warning message for each case. 2. Add a warning message for each case with an option to set the relevant disks' 'wipe after delete' value to true. 3. Don't add any warning message (i.e., CLOSE WONTFIX). clearing needinfo on me - let me know if my advice is needed here in any way (would need a little background on this issue though - I'm quite confused...). I suggest to clone this bug to 3.6 downstream to allow proper documentation as well Add a warning message for each case with an option to set the relevant disks' 'wipe after delete' value to true, sounds the right approach. Sean (In reply to Sean Cohen from comment #4) > I suggest to clone this bug to 3.6 downstream to allow proper documentation > as well I don't to have to manage two bugs simultaneously. Once this is MODIFIED and we're sure what the behavior should be, we'll open a documentation bug to make sure it's properly documented. Not worth the effort, closing. |