Bug 1381710 - [ocp3.2.1] user can not make use of environment variables to set openshift_cloudprovider_aws_{access,secret}_key within the ansible inventory
Summary: [ocp3.2.1] user can not make use of environment variables to set openshift_cl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 3.2.1
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1342028
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 19:04 UTC by Scott Dodson
Modified: 2016-10-27 16:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, environment variable lookups and other variable expansion within the ansible inventory would not be correctly interpreted. These variables are now interpreted correctly, for example: openshift_cloudprovider_aws_access_key="{{ lookup('env','AWS_ACCESS_KEY_ID') }}" causes the AWS_ACCESS_KEY_ID environment variable to be set as the AWS cloud provider access key.
Clone Of: 1342028
Environment:
Last Closed: 2016-10-27 16:13:43 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2122 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix update 2016-10-27 20:11:30 UTC

Comment 1 Scott Dodson 2016-10-04 19:32:18 UTC
https://github.com/openshift/openshift-ansible/pull/2545 backports PR cloned this to 3.2.1 because the QE had set aos-3.2.x? flag on original bug.

Comment 3 Johnny Liu 2016-10-19 10:52:21 UTC
Verified this bug with openshift-ansible-3.2.34-1.git.0.f26af07.el7.noarch, and PASS.

Environment variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY could set openshift_cloudprovider_aws_{access,secret}_key successfully in config files.

Comment 4 Johnny Liu 2016-10-19 11:56:38 UTC
Due to the latest 3.2 puddle is using ansible-2.2.0.0-0.62.rc1.el7.noarc which introduce new issue - BZ#1386654, it is blocking 3.2 install, move back this bug to ON_QA.

Comment 5 Johnny Liu 2016-10-25 11:20:52 UTC
Now BZ#1386654 is fixed, so according to comment 3, move this bug to "VERIFIED".

Comment 7 errata-xmlrpc 2016-10-27 16:13:43 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-2016:2122


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