Bug 1573490

Summary: A second VMware provider refresh problem (components not discovered)
Product: Red Hat CloudForms Management Engine Reporter: Ilanit Stein <istein>
Component: ProvidersAssignee: Adam Grare <agrare>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.9.0CC: gblomqui, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: vmware
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-01 14:26:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: VMware Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evm.log
none
automation.log none

Description Ilanit Stein 2018-05-01 14:01:44 UTC 
Description of problem:
On CFME-5.8.4.2, have vSphere provider (6.5). When added a second vSphere provider 6.0, the refresh was Never done.  
If running Configuration->"Refresh relationships and power states" - 
the refresh is done, and within minutes in provider details page, all it's component are displayed.

Later on, I removed the 1st vSphere, and added it back - Again the provider details page showed the refresh was never done.
and "Refresh relationship..." solved the problem.

Version-Release number of selected component (if applicable):
CFME-5.8.4/Vsphere 6.0, 6.5

How reproducible:
Occurred twice (each time I added a second VMware provider).
Comment 2 Ilanit Stein 2018-05-01 14:02:16 UTC 
Created attachment 1429180 [details]
evm.log
Comment 3 Ilanit Stein 2018-05-01 14:02:38 UTC 
Created attachment 1429181 [details]
automation.log
Comment 4 Adam Grare 2018-05-01 14:26:44 UTC 
Known issue, see https://bugzilla.redhat.com/show_bug.cgi?id=1439387

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