Bug 1333434 - 5.5.4.0 initial refresh missing portions of inventory
Summary: 5.5.4.0 initial refresh missing portions of inventory
Keywords:
Status: CLOSED DUPLICATE of bug 1333467
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Adam Grare
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-05 13:31 UTC by Alex Krzos
Modified: 2017-12-05 15:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-09 17:29:03 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evm.log showing two refreshes, first refresh only contains part of the inventory (1.36 MB, application/zip)
2016-05-05 13:34 UTC, Alex Krzos
no flags Details

Description Alex Krzos 2016-05-05 13:31:54 UTC
Description of problem:
I am adding a provider and the initial inventory only contains some of the full provider inventory.

Version-Release number of selected component (if applicable):
5.5.4.0 only (right now) 
I have not checked 5.6.x
5.5.3.2 does not display this behavior

How reproducible:
Only on large/xlarge environments (>1000vms seems to be the threshold to start seeing this)

Steps to Reproduce:
1. Add large or xlarge provider and view initial inventory
2.
3.

Actual results:
In two cases I saw 1360vms and 960vms in a second case

Expected results:
for large provider 3000vms

Additional info:
Kicking off a second refresh against the provider later on completes the inventory.

Comment 2 Alex Krzos 2016-05-05 13:34:52 UTC
Created attachment 1154209 [details]
evm.log showing two refreshes, first refresh only contains part of the inventory

Comment 3 Greg Blomquist 2016-05-05 13:59:40 UTC
I believe this is a dup of bug #1329417.

Comment 4 Adam Grare 2016-05-09 17:29:03 UTC

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


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