Bug 1260503

Summary:	The 'x' on the top right corner of the errata dialog doesn't close the dialog
Product:	[oVirt] ovirt-engine	Reporter:	Moti Asayag <masayag>
Component:	Frontend.WebAdmin	Assignee:	Alexander Wels <awels>
Status:	CLOSED CURRENTRELEASE	QA Contact:	movciari
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, ecohen, gklein, lsurette, mgoldboi, oourfali, rbalakri, yeylon
Target Milestone:	ovirt-3.6.1	Flags:	oourfali: ovirt-3.6.z? ylavi: planning_ack? oourfali: devel_ack+ rule-engine: testing_ack+
Target Release:	3.6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-16 12:20:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Moti Asayag 2015-09-07 06:22:33 UTC

Description of problem:
The 'x' icon on the top right corner of the errata dialog doesn't close the dialog. The dialog can only be closed by clicking on 'ok' button.

Version-Release number of selected component (if applicable):
commit 6b86f301d5eaba7ffa10b829bbcdc8d1acac3740

How reproducible:
always

Steps to Reproduce:
1. Open Errata dialog
2. Try to close it with the 'x' icon

Actual results:
Nothing.

Expected results:
Errata dialog should be closed

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 10:50:20 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Yaniv Lavi 2015-10-29 12:32:58 UTC

In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.

Comment 3 Sandro Bonazzola 2015-12-16 12:20:47 UTC

According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.