Bug 1516657

Summary: Infrastructure providers cannot be removed.
Product: Red Hat CloudForms Management Engine Reporter: Nisim Simsolo <nsimsolo>
Component: ProvidersAssignee: Hilda Stastna <hstastna>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.9.0CC: gblomqui, jfrey, jhardy, lsmola, nsimsolo, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-23 16:45:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Removing infrastructure provider - screen video none

Description Nisim Simsolo 2017-11-23 08:32:05 UTC 
Description of problem:
When trying to remove infrasturcture provider, it looks like it has been removed, but when refreshing the page/browser, the provider is still there.
This issue is true for VMware and RHV providers.

Please see screen video attached.

Version-Release number of selected component (if applicable):
cfme-5.9.0.10-1.el7cf.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Browse CFME UI -> Compute -> infrastructure -> providers
2. Check provider checkbox -> Configuration -> remove infrastructure providers from inventory. 
3. Refresh browser

Actual results:
Provider did not reomve

Expected results:
Provider should be removed.

Additional info:
screen video attached.
Comment 2 Nisim Simsolo 2017-11-23 08:33:58 UTC 
Created attachment 1358071 [details]
Removing infrastructure provider - screen video
Comment 3 Ladislav Smola 2017-11-23 14:08:49 UTC 
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1514334 ?
Comment 4 Hilda Stastna 2017-11-23 16:45:14 UTC 
Ladas, yes, this is a dup of 1514334 and this bug no longer exists
so I am closing the bug.

*** This bug has been marked as a duplicate of bug 1514334 ***