Bug 1494525
| Summary: | Can attach OVF-STORE as disk while creating a new VM | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Sandro Bonazzola <sbonazzo> | ||||||||||
| Component: | BLL.Storage | Assignee: | Tal Nisan <tnisan> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yosi Ben Shimon <ybenshim> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 4.2.0 | CC: | amureini, bugs, lveyde, tnisan | ||||||||||
| Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
ovirt-4.2+
|
||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | ovirt-engine-4.2.1.1 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-02-12 11:48:02 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
Sandro Bonazzola
2017-09-22 12:23:15 UTC
Created attachment 1329562 [details]
image selection dialog
Created attachment 1329564 [details]
image attached
I believe this is intentional. Tal? This was always the behavior, the disks list was not filtered when trying to attach to a VM, however the operation did and is still failing with "Cannot attach Virtual Disk. The operation is not supported for OVF_STORE disks." Having said that, after the latest changing regarding content type it now makes it easier to filter out disks that cannot be attached to a VM, Allon do you think that this is worth the effort? (In reply to Tal Nisan from comment #4) > This was always the behavior, the disks list was not filtered when trying to > attach to a VM, however the operation did and is still failing with "Cannot > attach Virtual Disk. The operation is not supported for OVF_STORE disks." Removing the Regression keyword based on that. > Having said that, after the latest changing regarding content type it now > makes it easier to filter out disks that cannot be attached to a VM, Allon > do you think that this is worth the effort? If it's an easy win, let's do it. Tested on ovirt-engine-4.2.1.1-0.1.el7.noarch and the disks list is filtered and no OVF_STORE disks appear in the list. See attached screen shots. Moving to VERIFIED Created attachment 1381313 [details]
images list
Created attachment 1381314 [details]
direct LUN
Forgot to mention that it was checked in both scenarios: 1. During the creation of the VM. 2. After VM creation: - Click on the VM name to open it's properties. - Under "disks" tab -> "attach" button on the top right This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |