Bug 1561071 – Wrong user for AWS smart state analysis

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1561071 - Wrong user for AWS smart state analysis

Summary:	Wrong user for AWS smart state analysis

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	cfme-amazon-smartstate (Show other bugs)
Sub Component:
Version:	5.9.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	GA
Target Release:	5.9.2
Assigned To:	Jerry Keselman
QA Contact:	Satyajit Bulage
Docs Contact:	Steve Bream

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1560125
Blocks:
	Show dependency tree / graph

Reported:	2018-03-27 10:56 EDT by Satoe Imaishi
Modified:	2018-05-07 17:14 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	5.9.2.1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1560125
Environment:
Last Closed:	2018-05-07 17:14:25 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1330	None	None	None	2018-05-07 17:14 EDT

Groups: None (edit)

Comment 3 Jerry Keselman 2018-04-10 13:21:56 EDT

Isn't that typically in @simaishi's purview?  Especially since is the cloned BZ that I never touched?

Comment 4 Jerry Keselman 2018-04-10 13:29:50 EDT

Moving to POST since this is an MR on Gitlab rather than a PR on Github.

Comment 5 Satyajit Bulage 2018-04-23 05:13:13 EDT

'cloud-user' is present in the settings and found that SSA is working fine on AWS.

Verified Version: 5.9.2.2.20180410215257_6961422

Comment 8 errata-xmlrpc 2018-05-07 17:14:25 EDT

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-2018:1330

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