Bug 1474816

Summary: [3.5] Host inventory configuration for limitSecretReferences: true
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Kenny Woodson <kwoodson>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.1CC: aos-bugs, eparis, erich, gpei, jialiu, jokerman, kwoodson, mmccomas, vwalek
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: 1442332 Environment:
Last Closed: 2017-08-16 07:59:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1442332    
Bug Blocks:    

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