Bug 1612086

Summary: Amazon API filter limit breaks targeted refresh for more than 200 items
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: ProvidersAssignee: Ladislav Smola <lsmola>
Status: CLOSED CURRENTRELEASE QA Contact: Matouš Mojžíš <mmojzis>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.3CC: dmetzger, gblomqui, jfrey, jhardy, obarenbo, rmanes, simaishi
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: provider:ec2
Fixed In Version: 5.10.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1651347 (view as bug list) Environment:
Last Closed: 2019-02-12 16:50:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1651347    
Attachments:
Description Flags
evm.log errors none

Description Matouš Mojžíš 2018-08-03 12:44:18 UTC 
Created attachment 1472977 [details]
evm.log errors

Description of problem:
PR: https://github.com/ManageIQ/manageiq-providers-amazon/pull/472

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

How reproducible:
Always

Steps to Reproduce:
Two ways to reproduce it:
1. Add an ec2 provider with public images enabled
2. Wait for refresh
3. Disable public images
4. Wait for refresh

1. Add an ec2 provider
2. Batch create more than 200 items that use targeted refresh in AWS

Actual results:
Refresh fails.

Expected results:


Additional info:
Comment 2 Ladislav Smola 2018-08-03 15:40:17 UTC 
https://github.com/ManageIQ/manageiq-providers-amazon/pull/472
Comment 3 Matouš Mojžíš 2018-08-29 15:23:46 UTC 
Verified in 5.10.0.12. 
Enable public images -> refresh ec2 provider -> disable public images -> refresh ec2 provider is working correctly.
I was unable to reproduce batch creating more than 200 objects in ec2, because it took some time to create them one by one and then they were refreshed by multiple targeted refreshes.
Comment 4 Satoe Imaishi 2018-11-19 18:42:57 UTC 
*** Bug 1647125 has been marked as a duplicate of this bug. ***