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

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.2.0
Hardware:	Unspecified Unspecified

Priority	low Severity medium
Target Milestone:	---
Target Release:	3.2.1
Assigned To:	Scott Dodson
QA Contact:	Johnny Liu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1342028
Blocks:
	Show dependency tree / graph

Reported:	2016-10-04 15:04 EDT by Scott Dodson
Modified:	2016-10-27 12:13 EDT (History)
CC List:	6 users (show)

See Also:
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.
Story Points:	---
Clone Of:	1342028
Environment:
Last Closed:	2016-10-27 12:13:43 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:2122	normal	SHIPPED_LIVE	OpenShift Container Platform atomic-openshift-utils bug fix update	2016-10-27 16:11:30 EDT

Groups: None (edit)

Comment 1 Scott Dodson 2016-10-04 15:32:18 EDT

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 06:52:21 EDT

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 07:56:38 EDT

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 07:20:52 EDT

Now BZ#1386654 is fixed, so according to comment 3, move this bug to "VERIFIED".

Comment 7 errata-xmlrpc 2016-10-27 12:13:43 EDT

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.