Bug 1370309 - missing rights to show AWS security groups caused null
Summary: missing rights to show AWS security groups caused null
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.6.2
Assignee: Ladislav Smola
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ec2
Depends On: 1370308
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 23:10 UTC by Dave Johnson
Modified: 2022-07-09 07:52 UTC (History)
4 users (show)

Fixed In Version: 5.6.2.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1370308
Environment:
Last Closed: 2016-10-04 14:32:07 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1996 0 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 18:26:13 UTC

Description Dave Johnson 2016-08-25 23:10:44 UTC 
+++ This bug was initially created as a clone of Bug #1370308 +++

Description of problem:
================================
Null security groups is caused by missing rights to show that security group, the current code was filtering them badly.
    https://github.com/ManageIQ/manageiq/pull/10659


Version-Release number of selected component (if applicable):
================================
5.6
Comment 1 Ladislav Smola 2016-09-01 07:35:26 UTC 
Darga backported
Comment 2 Matouš Mojžíš 2016-09-21 14:31:25 UTC 
Verified in 5.6.2.0. Security groups aren't null.
Comment 4 errata-xmlrpc 2016-10-04 14:32:07 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://rhn.redhat.com/errata/RHSA-2016-1996.html
Note You need to log in before you can comment on or make changes to this bug.