Bug 840558
| Summary: | [rhevm] [web-admin] Creating a V1 block data storage domain should be allowed in order to reinitialize a 3.0 DC with V1 block domains | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | vvyazmin <vvyazmin> | ||||
| Component: | ovirt-engine-userportal | Assignee: | Daniel Erez <derez> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | vvyazmin <vvyazmin> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.1.0 | CC: | abaron, amureini, dyasny, ecohen, hateya, iheim, Rhev-m-bugs, sgrinber, ykaul | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | 3.1.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | si16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-04 19:59:43 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: | |||||||
| Attachments: |
|
||||||
|
Description
vvyazmin@redhat.com
2012-07-16 15:17:45 UTC
Created attachment 598481 [details]
## Logs vdsm, rhevm, screen-shots
There is no point of allowing creation on V1 storage domain, it just leaves a door to nasty bugs in the upgrade process, rhevm 3.1 only supports 3.0 and 3.1 compatibility version, which means either v2 or v3 (in the coming build). please filter it out from the GUI. other than export/iso domains? (In reply to comment #3) > other than export/iso domains? correct. I assume they cannot be created from the API as well? (In reply to comment #7) > I assume they cannot be created from the API as well? Moving back to post seeing as current patch does not prevent it in API only in GUI. maybe should keep the api for now. 3.0 DC doesn't mean its not V1, and you need 'none' to reconstruct? (although, if there is more than a single storage domain, you don't need to add with none, and if it was a single storage domain, maybe we want to reconstruct on V2 (though we probably block from adding a V2 storage domain to a V1 DC) Users can upgrade from 3.0 with a DC containing only V1 storage domains. In such a scenario we must allow reinitializing the DC with a V1 storage domain, hence this is not a bug. need to revert the patch that was committed. patch sent upstream: http://gerrit.ovirt.org/#/c/7388/ patch merged upstream: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=aa4fc6b1a3289348a50d57d7c4c5baedb0120f88 Change-Id: Ib0dd0dd838b3a56b50fa7f9f93925a5002793e07 merged Succeeded create iSCSI Storage Domain, with format V1 that not attached to Data Center (Data Center == (none)) Failed attached to iSCSI Storage Domain v3.0 and v3.1 Warning message displayed on Admin UI Verified on RHEVM 3.1 - SI16 RHEVM: rhevm-3.1.0-14.el6ev.noarch VDSM: vdsm-4.9.6-31.0.el6_3.x86_64 LIBVIRT: libvirt-0.9.10-21.el6_3.4.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6_3.1.x86_64 SANLOCK: sanlock-2.3-3.el6_3.x86_64 |