Bug 1983935
| Summary: | [IBM Z]: Creating AWS and IBMCOS backing store with yaml reports INVALID_ENDPOINT | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Sravika <sbalusu> | ||||||||
| Component: | Multi-Cloud Object Gateway | Assignee: | Romy Ayalon <rayalon> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Raz Tamir <ratamir> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.8 | CC: | etamir, ocs-bugs | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-07-28 10:45:18 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Sravika
2021-07-20 08:29:09 UTC
Created attachment 1803532 [details]
openshift-console-screenshot
Same error has been observed while creating ibmcos backing store with the following yaml files.
ibmcossecret.yaml:
apiVersion: v1
kind: Secret
metadata:
name: ibmcosbs-secret
namespace: openshift-storage
type: Opaque
data:
IBM_COS_ACCESS_KEY_ID: <IBM COS ACCESS KEY ID ENCODED IN BASE64>
IBM_COS_SECRET_ACCESS_KEY: <IBM COS SECRET ACCESS KEY ENCODED IN BASE64>
ibmcosbs.yaml:
apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
finalizers:
- noobaa.io/finalizer
labels:
app: noobaa
name: ibmcosbsyaml
namespace: openshift-storage
spec:
ibmCos:
endpoint: https://s3.eu-de.cloud-object-storage.appdomain.cloud
secret:
name: ibmcosbs-secret
namespace: openshift-storage
targetBucket: myibmcosbucket
type: ibm-cos
Uploading the description of the backingstore as attachment
Created attachment 1803666 [details]
ibmcos backingstore description
Hi @sbalusu you have a trailing /n character in the secret key and access key you provided to the aws backingstore (probably the IBM has the same issue). please try it again without the /n and let us know if we can close the bug. @Rom Ayalon: I see a need info flag set on my name, but I cannot see any comment. Can you please make the comment public. @rayalon: I do not find any trailing character in both aws and ibm secret files. Please find the yamllint outputs of both the yaml files as follows: # yamllint awssecret.yaml awssecret.yaml 1:1 warning missing document start "---" (document-start) 9:81 error line too long (81 > 80 characters) (line-length) yamllint ibmcossecret.yaml ibmcossecret.yaml 1:1 warning missing document start "---" (document-start) 9:81 error line too long (97 > 80 characters) (line-length) The line too log error is on the base64 encoded "AWS_SECRET_ACCESS_KEY" try to check if you encoded it inside the base64, I specifically see in the logs that there are trailing /n in both secret key and access key. @rayalon: The keys are base64 encoded only once and I verified it. After discussing with @rayalon on chat , figured out that the base64 encoding has added a trailing newline character to the access key and secret access key. The "-n" option while encoding (echo -n <key> | base64) has truncated the trailing line and the backingstore creation was successful. The issue can be closed. |