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:
https://github.com/ManageIQ/manageiq-providers-amazon/pull/93
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
https://github.com/ManageIQ/manageiq-content/pull/26
Implemented via https://github.com/ManageIQ/manageiq-content/pull/183
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days