Bug 1371222

Summary: EC2 autorefresh works only for items associated to instance/image
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: ProvidersAssignee: Ladislav Smola <lsmola>
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: gblomqui, jfrey, jhardy, lsmola, mhild, obarenbo, simaishi
Target Milestone: GAFlags: simaishi: needinfo? (gblomqui)
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ec2
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:07:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:

Description Matouš Mojžíš 2016-08-29 15:49:21 UTC
Description of problem:
Issue on upstrem master: https://github.com/ManageIQ/manageiq/issues/10591

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

How reproducible:
Always

Steps to Reproduce:
1. Add an ec2 provider.
2. Add/delete/update key pairs/ security groups/ EIPs, which are not associated to any instance.
3.

Actual results:
No autorefresh occurs.

Expected results:
Autorefresh should occur.

Additional info:

Comment 5 Marcel Hild 2017-04-24 15:14:25 UTC
indeed - the PR has been reverted by https://github.com/ManageIQ/manageiq-providers-amazon/pull/114

Ladas, should we trigger a refresh on AWS_EC2_EIP_CREATE ? 
Or do you want to work forward with https://github.com/ManageIQ/manageiq-content/pull/26 ?

changing back to ASSIGNED and assigning to ladas

Comment 6 Ladislav Smola 2017-04-24 15:25:29 UTC
https://github.com/ManageIQ/manageiq-content/pull/26

Comment 8 Ladislav Smola 2017-10-12 15:30:56 UTC
Implemented via

https://github.com/ManageIQ/manageiq-content/pull/183

Comment 14 errata-xmlrpc 2018-03-01 13:07:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0380