Bug: Bad reading of the AWS credentials file #621
Description
Contact Details
Describe bug
When creating an AWS credentials file on Windows 10, the file is created with cr/nl characters at the end of every line.
Then, the oadp-*-aws-registry pod can't read the aws_access_key_id and displays an error message: CreateContainerConfigError (see operator pod error message below).
The same file created on Linux with only nl characters at the end of every line works perfectly fine.
What happened?
Whatever platform [Linux/Microsoft Windows/MacOs] you use to create the credentials, the AWS keys should be read fine.
OADP Version
1.0.1 (Stable)
OpenShift Version
4.10
Velero pod logs
No response
Restic pod logs
No response
Operator pod logs
2022-04-05T14:21:53.588Z INFO controller.dataprotectionapplication Error finding AWS Profile for the supplied AWS credential {"reconciler group": "oadp.openshift.io", "reconciler kind": "DataProtectionApplication", "name": "dpa-sample", "namespace": "openshift-adp"}
2022-04-05T14:21:53.588Z INFO controller.dataprotectionapplication Error parsing provider secret cloud-credentials for backupstoragelocation openshift-adp/dpa-sample-1 {"reconciler group": "oadp.openshift.io", "reconciler kind": "DataProtectionApplication", "name": "dpa-sample", "namespace": "openshift-adp"}New issue
- This issue is new