Red Hat Bugzilla – Bug 1552290
AWS Smartstate Does Not Fail Gracefully if AMI To run Analysis Agent is Unavailable
Last modified: 2018-05-07 16:43:44 EDT
New commit detected on ManageIQ/manageiq-providers-amazon/gaprindashvili: https://github.com/ManageIQ/manageiq-providers-amazon/commit/f46819b030e736bd6dac69b8a2bfa87347766d8b commit f46819b030e736bd6dac69b8a2bfa87347766d8b Author: Richard Oliveri <oliveri.richard.github@gmail.com> AuthorDate: Thu Feb 15 13:18:49 2018 -0500 Commit: Richard Oliveri <oliveri.richard.github@gmail.com> CommitDate: Thu Feb 15 13:18:49 2018 -0500 Merge pull request #411 from jerryk55/raise_if_ami_not_visible Raise Exception if AMI not visible (cherry picked from commit 4bf09ce4679e27efb6a59b9fa332b435f4231e63) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1552290 app/models/manageiq/providers/amazon/agent_coordinator.rb | 1 + 1 file changed, 1 insertion(+) https://github.com/ManageIQ/manageiq-providers-amazon/commit/38c2bdb9b9d09d52111869afa946bb49c3cafab2 commit 38c2bdb9b9d09d52111869afa946bb49c3cafab2 Author: Richard Oliveri <oliveri.richard.github@gmail.com> AuthorDate: Sun Feb 18 19:04:41 2018 -0500 Commit: Richard Oliveri <oliveri.richard.github@gmail.com> CommitDate: Sun Feb 18 19:04:41 2018 -0500 Merge pull request #412 from jerryk55/cleanup_jobs_if_ami_unavailable Cleanup Smartstate Requests When AMI Unavailable for Agent (cherry picked from commit ba9939f4615167278c81ce787ed35b3e2e3d32c1) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1552290 app/models/manageiq/providers/amazon/agent_coordinator.rb | 47 +- 1 file changed, 46 insertions(+), 1 deletion(-)
After putting wrong AMI image name in settings, agent is not properly setup. As result, able to see proper error message. Verified Version: 5.9.2.3.20180419182310_cab2891
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:1328