Bug 1974640
| Summary: | When installing on AWS, AWS_SHARED_CREDENTIALS_FILE is only obeyed for reading and not for writing credentials | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Pierre Prinetti <pprinett> |
| Component: | Installer | Assignee: | Aditya Narayanaswamy <anarayan> |
| Installer sub component: | openshift-installer | QA Contact: | Yunfei Jiang <yunjiang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | anarayan, esimard, padillon |
| Version: | 4.8 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When AWS_SHARED_CREDENTIALS_FILE is pointing to an empty file, the installer asks the user for credentials and creates a file at location "~/.aws/credentials" irrespective of what is mentioned in the AWS_SHARED_CREDENTIALS_FILE location.
Adding a fix that will create a new file in the location specified in the given env variable. This fix does not create a file if the location specified has a file with invalid credentials and asks the user to change the location as a safety measure to prevent overwriting user data.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-18 17:35:57 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: | |||
|
Description
Pierre Prinetti
2021-06-22 08:38:10 UTC
This has been reviewed, and we will target a fix after the feature freeze. Will address this in a future sprint. Needs prioritized. verified. PASS. OCP version:4.9.0-0.nightly-2021-08-25-185404 > non-exist AWS_SHARED_CREDENTIALS_FILE export AWS_SHARED_CREDENTIALS_FILE=/tmp/non-exist-file ./openshift-install create install-config --dir cluster2 ? SSH Public Key /home/cloud-user/.ssh/openshift-qe.pub ? Platform aws ? AWS Access Key ID aaa ? AWS Secret Access Key [? for help] *** INFO Writing AWS credentials to "/tmp/non-exist-file" (https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html) cat /tmp/non-exist-file ; https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html [default] aws_access_key_id = aaa aws_secret_access_key = bbb > empty AWS_SHARED_CREDENTIALS_FILE export AWS_SHARED_CREDENTIALS_FILE= ./openshift-install create install-config --dir cluster4 ? SSH Public Key /home/cloud-user/.ssh/openshift-qe.pub ? Platform aws INFO Credentials loaded from the "default" profile in file "/home/cloud-user/.aws/credentials" > invalid ini file export AWS_SHARED_CREDENTIALS_FILE=/tmp/invalid-cred ./openshift-install create install-config --dir cluster5 ? SSH Public Key /home/cloud-user/.ssh/openshift-qe.pub ? Platform aws ? AWS Access Key ID assss ? AWS Secret Access Key [? for help] ******* INFO Writing AWS credentials to "/tmp/invalid-cred" (https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html) cat /tmp/in-valid-cred aws_access_key_id = AKIA aws_secret_access_key = H0/6 [default] aws_access_key_id = assss aws_secret_access_key = sasdasd 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759 |