Description of problem: Version-Release number of selected component (if applicable): 5.11.0.21 How reproducible: Always Steps to Reproduce: 1. Add classic Elastic(Floating) IP in AWS directly 2. Wait for classic IP to appear 3. Actual results: Ip address is not in CFME until refreshed manually. When adding in AWS VPC EIP it's added by targeted refresh. Expected results: Additional info:
https://github.com/ManageIQ/manageiq-providers-amazon/pull/618
New commit detected on ManageIQ/manageiq-providers-amazon/ivanchuk: https://github.com/ManageIQ/manageiq-providers-amazon/commit/a1b9403eba0efb5e8fae361826caca325b7f90b8 commit a1b9403eba0efb5e8fae361826caca325b7f90b8 Author: Adam Grare <agrare> AuthorDate: Thu Apr 23 12:39:01 2020 +0000 Commit: Adam Grare <agrare> CommitDate: Thu Apr 23 12:39:01 2020 +0000 Merge pull request #618 from djberg96/floating_ip_target_collection Update Floating IP target and event collection (cherry picked from commit ba32611b728bd7c915151635e682474c125f8c0d) https://bugzilla.redhat.com/show_bug.cgi?id=1746860 app/models/manageiq/providers/amazon/cloud_manager/event_target_parser.rb | 1 + app/models/manageiq/providers/amazon/inventory/collector/target_collection.rb | 3 +- spec/models/manageiq/providers/amazon/cloud_manager/event_target_parser_spec.rb | 11 +- spec/vcr_cassettes/manageiq/providers/amazon/cloud_manager/refresher_targeted/ec2_classic_vm_and_lb_full_refresh.yml | 67 +- spec/vcr_cassettes/manageiq/providers/amazon/cloud_manager/refresher_targeted/orchestration_stacks_nested_with_vm.yml | 92 +- spec/vcr_cassettes/manageiq/providers/amazon/cloud_manager/refresher_targeted/vpc_vm_with_floating_ip_and_lbs_full_refresh.yml | 88 +- spec/vcr_cassettes/manageiq/providers/amazon/cloud_manager/refresher_targeted/vpc_vm_with_public_ip_and_template.yml | 69 +- 7 files changed, 274 insertions(+), 57 deletions(-)
FIXED. Verified on 5.11.6.0.20200526234234_3fcafeb. Steps taken to verify - 1. Add AWS provider on CFME. 2. Provision an instance. 3. Notice the list of IPs. 4. Allocate EIP to provider. 5. Wait for a minute. 6. Navigate to the Instance's detail page and notice the EIP appear in the IP's list. 7. Release the EIP. 8. Wait for a minute. 9. Navigate to the Instance's detail page and notice the EIP disappear from the IP's list.
Let me know if I missed out on verifying something else.
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-2020:2480