Description of problem: Provisioning an AWS instance occasionally fails with the following error: MIQ(ManageIQ::Providers::Amazon::CloudManager::Provision#provision_error) [[Aws::EC2::Errors::InvalidInstanceIDNotFound]: The instance ID 'i-xxxxxxxxxxxx' does not exist] encountered during phase [poll_clone_complete]
https://github.com/ManageIQ/manageiq/pull/20122
https://github.com/ManageIQ/manageiq-providers-amazon/pull/604
New commit detected on ManageIQ/manageiq-providers-amazon/jansa: https://github.com/ManageIQ/manageiq-providers-amazon/commit/0ef7a2c2611723eab527ebf04fad3747f0168beb commit 0ef7a2c2611723eab527ebf04fad3747f0168beb Author: Adam Grare <agrare> AuthorDate: Fri Mar 6 18:14:32 2020 +0000 Commit: Adam Grare <agrare> CommitDate: Fri Mar 6 18:14:32 2020 +0000 Merge pull request #604 from A-Beck/check-instance-existance-before-getting-status Check instance exists before getting status during provisioning (cherry picked from commit 262d51c7ce5d41e061960618b816255bf5282e8b) https://bugzilla.redhat.com/show_bug.cgi?id=1830305 app/models/manageiq/providers/amazon/cloud_manager/provision/cloning.rb | 4 +- 1 file changed, 3 insertions(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq-providers-amazon/ivanchuk: https://github.com/ManageIQ/manageiq-providers-amazon/commit/3ddfa00cddfa93722d33801fc7c80bfd433ffb4d commit 3ddfa00cddfa93722d33801fc7c80bfd433ffb4d Author: Adam Grare <agrare> AuthorDate: Fri Mar 6 18:14:32 2020 +0000 Commit: Adam Grare <agrare> CommitDate: Fri Mar 6 18:14:32 2020 +0000 Merge pull request #604 from A-Beck/check-instance-existance-before-getting-status Check instance exists before getting status during provisioning (cherry picked from commit 262d51c7ce5d41e061960618b816255bf5282e8b) https://bugzilla.redhat.com/show_bug.cgi?id=1830305 app/models/manageiq/providers/amazon/cloud_manager/provision/cloning.rb | 4 +- 1 file changed, 3 insertions(+), 1 deletion(-)
FIXED. Verified on 5.11.6.0.20200526234234_3fcafeb. Was able to provision the AWS instance without any error.
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