Bug 1381710
| Summary: | [ocp3.2.1] user can not make use of environment variables to set openshift_cloudprovider_aws_{access,secret}_key within the ansible inventory | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.2.0 | CC: | abutcher, aos-bugs, bleanhar, jialiu, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 16:13:43 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: | 1342028 | ||
| Bug Blocks: | |||
|
Comment 1
Scott Dodson
2016-10-04 19:32:18 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.
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. Now BZ#1386654 is fixed, so according to comment 3, move this bug to "VERIFIED". 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 |