Bug 1284938 - Containers SmartState Analysis should use the management-infra namespace
Summary: Containers SmartState Analysis should use the management-infra namespace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.5.0
Assignee: Federico Simoncelli
QA Contact: Einat Pacifici
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-24 13:53 UTC by Federico Simoncelli
Modified: 2015-12-08 13:50 UTC (History)
6 users (show)

Fixed In Version: 5.5.0.12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:50:02 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-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Federico Simoncelli 2015-11-24 13:53:39 UTC
Description of problem:
Since the OpenShift Service Account creation has been made stricter we need to use the "management-infra" namespace for SmartState Analysis (and make it configurable).

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


How reproducible:
100%

Steps to Reproduce:
1. Configure the Cloudforms Service Account with admin privileges over the namespace "management-infra"

Actual results:
Smart state analysis fails because it's using the "default" namespace

Expected results:
Smart state analysis shouldn't fail and use the "management-infra" namespace


Additional info:

Comment 2 Einat Pacifici 2015-12-02 09:31:22 UTC
Verified. 
Management-infra namespace is now used. 
Sample log line:
"creating pod management-infra/manageiq-img-scan-ca4d7b1b9a51 to analyze docker image ca4d7b1b9a51f72ff4da652d96943f657b4898889924ac3dae5df958dba0dc4a:"

Comment 4 errata-xmlrpc 2015-12-08 13:50:02 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/RHSA-2015:2551


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