Bug 1539310
Summary: | ASB bootstrap fail while using file authenticate type since failed to read registry credentials from file | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
Component: | Service Broker | Assignee: | Dylan Murray <dymurray> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, jiazha, jmatthew, zitang |
Target Milestone: | --- | ||
Target Release: | 3.9.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 18:01:30 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: | |||
Bug Blocks: | 1535026 |
Comment 1
Dylan Murray
2018-01-30 15:47:11 UTC
Zhang, I can confirm that `auth_type`: file works for me. I believe the problem is that you never created an associated file in the asb deployment config. To test again, you must first create file reg-creds.yaml: --- username: <username> password: <password> Create a secret from this file: oc create secret generic registry-credentials-secret --from-file reg-creds.yaml Edit the asb deployment config to mount this file into /tmp/registry-credentials/reg-creds.yaml: under containers/volumeMounts: - mountPath: /tmp/reistry-credentials name: reg-auth under volumes: - name: reg-auth secret: defaultMode: 420 secretName: registry-credentials-secret Set auth_name to /tmp/registry-credentials/reg-creds.yaml This worked for me using the `openshift` adapter and using rocketchat as the image. Dylan, LGTM after double check, that because my mount not succeed. Thanks. 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/RHSA-2018:2013 |