Bug 1474816 - [3.5] Host inventory configuration for limitSecretReferences: true
Summary: [3.5] Host inventory configuration for limitSecretReferences: true
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.z
Assignee: Kenny Woodson
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On: 1442332
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-25 12:45 UTC by Scott Dodson
Modified: 2017-08-16 07:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
The master configuration item "serviceAccountConfig.limitSecretReferences" may now be set via the installation playbooks by setting the variable openshift_master_saconfig_limitsecretreferences=true or openshift_master_saconfig_limitsecretreferences=false.
Clone Of: 1442332
Environment:
Last Closed: 2017-08-16 07:59:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2482 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-08-16 11:58:57 UTC

Comment 2 Kenny Woodson 2017-07-25 13:50:10 UTC 
This has been backported to release-1.5 branch here: https://github.com/openshift/openshift-ansible/pull/4860
Comment 4 Gaoyun Pei 2017-08-09 02:52:58 UTC 
Verify this bug with openshift-ansible-3.5.110-1.git.0.6f1f193.el7.noarch.rpm

Once set openshift_master_saconfig_limitsecretreferences=true in ansible inventory, after installation finished, check master config yaml file, limitSecretReferences was set to true
serviceAccountConfig:
  limitSecretReferences: true

When without openshift_master_saconfig_limitsecretreferences=true set in ansible inventory file, limitSecretReferences was set to false by default
serviceAccountConfig:
  limitSecretReferences: False
Comment 6 errata-xmlrpc 2017-08-16 07:59:16 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-2017:2482
Note You need to log in before you can comment on or make changes to this bug.