Bug 1557770

Summary:	Webadmin-imageIO - 'Cancel' option should be removed from download disk
Product:	[oVirt] ovirt-engine	Reporter:	Avihai <aefrat>
Component:	BLL.Storage	Assignee:	Idan Shaby <ishaby>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.2	CC:	bugs, ishaby, ylavi
Target Milestone:	ovirt-4.2.4	Flags:	rule-engine: ovirt-4.2+ ylavi: exception+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-26 08:38:32 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:

Description Avihai 2018-03-18 14:05:27 UTC

Description of problem:
As part of bug 1539363, download operation is now canceled automatically so no need for this option in webadmin - please remove it .

Version-Release number of selected component (if applicable):
4.2.2.4-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1.Webadmin -> disks -> choose a disk -> download

Actual results:
Cancel option is there

Expected results:
Cancel option should not be there

Additional info:

Comment 1 Daniel Erez 2018-03-18 14:57:32 UTC

@Idan - iirc, we've kept the cancel button just to allow cancellation of old downloads that were stuck in paused status. Maybe we can just automatically cancel those downloads as well? I.e. add to the auto cancel mechanism support for paused downloads? Or is it problematic?

Comment 2 Idan Shaby 2018-03-19 08:16:24 UTC

I can't think of anything problematic here, so I guess that it can be pretty easy to implement.

Comment 3 Avihai 2018-05-28 08:12:38 UTC

Verified on engine 4.2.4-0.1

Comment 4 Sandro Bonazzola 2018-06-26 08:38:32 UTC

This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.