Bug 1760642 - EC2 SSA is failing by using existing AMI image.
Summary: EC2 SSA is failing by using existing AMI image.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.10.12
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.10.12
Assignee: Satoe Imaishi
QA Contact: Satyajit Bulage
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-11 02:37 UTC by Satyajit Bulage
Modified: 2019-11-06 08:58 UTC (History)
4 users (show)

Fixed In Version: 5.10.12.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 08:58:33 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
simaishi: mirror+


Attachments (Terms of Use)

Description Satyajit Bulage 2019-10-11 02:37:34 UTC
Description of problem: SSA on EC2 instance is failing to create instance in EC2 due to old AMI present there.


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


How reproducible:100%


Steps to Reproduce:
1.Add EC2 provider with(I am using Satoe's private docker image.)
2.Add SmartState Docker credentials.
3.

Actual results: SSA didn't complete, throws error at Creating Instance.


Expected results:SSA should be finish without any error.


Additional info:
Here is BZ on CF 5.11 fixed for reference --> https://bugzilla.redhat.com/show_bug.cgi?id=1745599#c18

Comment 2 Satyajit Bulage 2019-10-11 02:50:41 UTC
EC2 SSA is failing due to AMI image: RHEL-Atomic_7.4_HVM_GA-20180104-x86_64-1-Access2-GP2

EC2 SSA is not failing after using AMI Image: RHEL-Atomic_7.7_HVM_GA-20190923-x86_64-0-Access2-GP2

Comment 8 Satyajit Bulage 2019-10-25 12:46:25 UTC
Able to see new AMI image "RHEL-Atomic_7.7_HVM_GA-20190923-x86_64-0-Access2-GP2" used to launch Docker instance in the CFME 5.10.12.1.

Verified Version: 5.10.12.1.20191022171907_f883bde

Comment 10 errata-xmlrpc 2019-11-06 08:58:33 UTC
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/RHBA-2019:3268


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