Bug 1497839 - When Secrets are defined the APB Pod is not run in the transient namespace
Summary: When Secrets are defined the APB Pod is not run in the transient namespace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.7.0
Assignee: Shawn Hurley
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 20:18 UTC by Shawn Hurley
Modified: 2017-11-28 22:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-28 22:14:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Shawn Hurley 2017-10-02 20:18:27 UTC 
Description of problem:
When secrets are defined to be used with an APB by the administrator, then the APB is not launched in the transient namespace

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


How reproducible:
Always

Steps to Reproduce:
1. Set up broker with secrets defined for a APB
2. Provision that APB
3.

Actual results:
Runs APB pod in ansible-service-broker namespace

Expected results:
Should run APB in a transient namespace.

Additional info:
Comment 1 weiwei jiang 2017-10-12 02:43:27 UTC 
Looks like this will fix https://bugzilla.redhat.com/show_bug.cgi?id=1496688 also.
Comment 2 Shawn Hurley 2017-10-16 12:42:26 UTC 
Fixed with PR: https://github.com/openshift/ansible-service-broker/pull/473
Comment 7 errata-xmlrpc 2017-11-28 22:14: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/RHSA-2017:3188
Note You need to log in before you can comment on or make changes to this bug.