Bug 1528804

Summary: 'Remove' button should be disabled for OVF_STORE disks with status other than ILLEGAL
Product: [oVirt] ovirt-engine Reporter: Yosi Ben Shimon <ybenshim>
Component: Frontend.WebAdminAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, lsvaty, tnisan
Target Milestone: ovirt-4.2.1Flags: rule-engine: ovirt-4.2+
lsvaty: testing_ack+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:48:22 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 Flags
Remove button enabled none

Description Yosi Ben Shimon 2017-12-24 09:38:32 UTC
Created attachment 1371858 [details]
Remove button enabled

Description of problem:
The 'Remove' button is enabled and can select an OVF_STORE to remove from the storage domain for OVF disks with status other than ILLEGAL.
When trying to actually remove the OVF_STORE disk, i get an error says:
'Error while executing action: Cannot remove Virtual Disk. The operation can be performed only for OVF disks that are in ILLEGAL status.'

Version-Release number of selected component (if applicable):
WebAdmin version: 4.2.0.2-0.1.el7

How reproducible:
always.

Steps to Reproduce:
1. Go to Storage -> Domains from the left side menu.
2. Click on the storage domain name.
3. Select the 'Disks' tab.
4. Select an OVF_STORE and mark the row.

Actual results:
The 'Remove' button is enabled

Expected results:
The 'Remove' button disabeld.

Additional info:

Comment 1 Yosi Ben Shimon 2018-01-09 09:33:40 UTC
Tested and the "remove" button is enabled only when the OVF_STORE status is ILLEGAL

Comment 2 Sandro Bonazzola 2018-02-12 11:48:22 UTC
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.