Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686940 - cfme-amazon-smartstate tracker bug for 5.10.2
Summary: cfme-amazon-smartstate tracker bug for 5.10.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: cfme-amazon-smartstate
Version: 5.10.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.10.2
Assignee: Satoe Imaishi
QA Contact: Satyajit Bulage
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-08 17:13 UTC by Satoe Imaishi
Modified: 2019-04-02 08:36 UTC (History)
2 users (show)

Fixed In Version: 5.10.2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-02 08:36:22 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0696 None None None 2019-04-02 08:36:22 UTC

Description Satoe Imaishi 2019-03-08 17:13:53 UTC
Tracker bug for 5.10.2 cfme-amazon-smartstate image

Comment 3 Satyajit Bulage 2019-04-02 04:26:49 UTC
Able to scan EC2 Instance, using Satoe's Private docker image. (RHEL AMI image used with different timestamp b/c same image available as private and public).

Verified Version: 5.10.2.2.20190319204241_4304a7d

Comment 5 errata-xmlrpc 2019-04-02 08:36:22 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:0696


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