Bug 1547228 - AWS Smartstate Does Not Fail Gracefully if AMI To run Analysis Agent is Unavailable
Summary: AWS Smartstate Does Not Fail Gracefully if AMI To run Analysis Agent is Unava...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Jerry Keselman
QA Contact: Satyajit Bulage
URL:
Whiteboard:
Depends On:
Blocks: 1552290
TreeView+ depends on / blocked
 
Reported: 2018-02-20 19:17 UTC by Jerry Keselman
Modified: 2019-02-11 13:59 UTC (History)
3 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1552290 (view as bug list)
Environment:
Last Closed: 2019-02-11 13:59:04 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jerry Keselman 2018-02-20 19:17:11 UTC
Description of problem:

When the AMI specified to run the Smartstate Analysis Engine on AWS is not available, there is no indication in the UI that a failure has occurred.  The job will appear to be running until it times out after 50 minutes.  There are basically two issues with this - 1) There should be an appropriate failure and error indicated in the UI.  2) The job that has been submitted on the AWS SQS queue should be removed.

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


How reproducible:

If the AMI specified in the production.yml file is not available, this will happen.


Steps to Reproduce:
1.
2.
3.

Actual results: Job times out.

Expected results: An error is shown in the UI and the job is removed from SQS.


Additional info:

Comment 2 Jerry Keselman 2018-02-20 19:19:40 UTC
The following PRs have been added to handle this issue:  

https://github.com/ManageIQ/manageiq-providers-amazon/pull/412

and

https://github.com/ManageIQ/manageiq-providers-amazon/pull/411.

THey should be backported to Gaprindashvili and Fine.

Comment 4 Satyajit Bulage 2018-11-06 10:39:04 UTC
Able to see the error message, after replacing correct AMI with wrong AMI image.

Verified Version: 5.10.0.22.20181030184024_26956a0


Note You need to log in before you can comment on or make changes to this bug.