Bug 1247065 – CFME doesn't complain about importing duplicate widgets

Bug 1247065 - CFME doesn't complain about importing duplicate widgets

Summary:	CFME doesn't complain about importing duplicate widgets

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	UI - OPS (Show other bugs)
Sub Component:
Version:	5.4.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low
Target Milestone:	GA
Target Release:	5.5.0
Assigned To:	Dan Clarizio
QA Contact:	Dave Johnson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-07-27 05:17 EDT by Nandini Chandra
Modified:	2015-11-11 15:32 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-07-27 18:37:52 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
screenshot of import widget page (73.89 KB, image/png) 2015-07-27 05:17 EDT, Nandini Chandra	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Nandini Chandra 2015-07-27 05:17:55 EDT

Created attachment 1056530 [details]
screenshot of import widget page

Description of problem:
----------------------


Version-Release number of selected component (if applicable):
--------------------
5.4.1


How reproducible:
-----------------
Always


Steps to Reproduce:
------------------
1.Import a widget
2.Upload the exact same yml file from the previous step for importing again
3.Notice that although 'Status' shows the message that the object already exists in the DB with the same name,the Commit button is still enabled and CFME allows this file to be committed again.

Actual results:
---------------
CFME doesn't complain about importing duplicate widgets


Expected results:
----------------
CFME should prevent this.


Additional info:
---------------

Note You need to log in before you can comment on or make changes to this bug.