Bug 1518385

Summary:	Adding new provider doesn't always automatically refresh the provider
Product:	Red Hat CloudForms Management Engine	Reporter:	Jeffrey Cutter <jcutter>
Component:	Providers	Assignee:	Adam Grare <agrare>
Status:	CLOSED DUPLICATE	QA Contact:	Dave Johnson <dajohnso>
Severity:	low	Docs Contact:
Priority:	medium
Version:	5.9.0	CC:	gblomqui, jcutter, jfrey, jhardy, 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-29 00:52:09 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:

Description Jeffrey Cutter 2017-11-28 19:24:59 UTC

Description of problem:

I have noticed on prior versions also that sometimes when adding a very small provider that takes no time to refresh, it doesn't automatically refresh when adding the provider.  Requesting a manual refresh will trigger it and it completes promptly.

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

5.9.0.11.20171127204214_e316988

How reproducible:

Intermittent.

Steps to Reproduce (what I just did):
1. Add first vcenter provider (it refreshed).
2. Add second vcenter provider (tiny, 2 host, 2 VMs) (wait 10 minutes, still no data, manual refresh and data is there almost immediately).
3. Add a first RHV provider (it refreshed and data is there almost immediately).

Actual results:

Second VMware provider did not automatically refresh (immediately at least).

Expected results:

All provider should refresh promptly upon being added.

Additional info:

Both vCenters are 6.5.

Comment 3 Adam Grare 2017-11-28 21:45:22 UTC

I believe this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1439387

Has to do with full refreshes being triggered by the vim broker, not by the refresh worker when it starts up and the vim broker only "starts" when the first provider is added or on full system restarts.

Comment 4 Jeffrey Cutter 2017-11-28 23:09:27 UTC

We were able to replicate it 2 more times, but as Adam Grare points out, this does appear to be a duplicate.  I stood up 3 different appliances to test this and have the logs if they are of any use, I can get them.  I also confirmed the UI is displaying the same as the VMDB.

Comment 5 Adam Grare 2017-11-29 00:52:09 UTC

Thanks Jeff, so this should only impact VMware and once you add all providers if you either manually refresh all but the first or restart the appliance everything should work normally.

I'll close this but if either of those aren't true please re-open

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