Bug: Setting `NoDefaultBackupLocation` still requires a cloud-credentials secret

[tkagn]

Contact Details

No response

Describe bug

Add veloro instance with "noDefaultBackupLocation: true" without cloud-credentials secret in namespace results in velero pods in pending state.

Create cloud-credentials secret with empty values

kind: Secret
apiVersion: v1
metadata:
name: cloud-credentials
namespace:
cloud: >-
base64 encoding of AWS credential file
type: Opaque

What happened?

Expected Velero pods to be in running state.

OADP Version

0.4.x (Beta)

OpenShift Version

4.8

Velero pod logs

No response

Restic pod logs

No response

Operator pod logs

credentials file not found

New issue

• This issue is new

[savitharaghunathan]

Hi @tkagn, I followed the steps you have mentioned in the description and unable to reproduce the issue. Once I created an empty secret called cloud-credentials, velero pod started and the CR reconciled successfully. Are you still seeing this issue?

[tkagn]

Hi Savitha, The issue was that the cloud-credential had to exist even though there was not backupservicelocation set. v/r

…

On Mon, Nov 22, 2021 at 3:06 PM Savitha Raghunathan < ***@***.***> wrote: Hi @tkagn <https://github.com/tkagn>, I followed the steps you have mentioned in the description and unable to reproduce the issue. Once I created an empty secret called cloud-credentails, velero pod started and the CR reconciled successfully. Are you still seeing this issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVDR2MSRR74EVP5KARHIFTUNKPD5ANCNFSM5G5H6ISA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Stephen Wilson Senior Storage Consultant Red Hat <https://www.redhat.com/> ***@***.*** M: (601)479-6562 <https://www.redhat.com/>

[savitharaghunathan]

Got it. Sorry I interpreted it the other way. Will take a look into it. Thanks for reporting the issue

[kaovilai]

@tkagn cloud-credentials are still used for other components beyond backup location.. such as for volume snapshotting if you are using the aws plugin. If you did not add aws plugin then we'll have to check where else this check is occuring.

[tkagn]

Understood. This was for a velero instance that would eventually backup to an external S3 MCG/NooBaa bucket

…

On Tue, Nov 23, 2021 at 10:14 AM Tiger Kaovilai ***@***.***> wrote: @tkagn <https://github.com/tkagn> cloud-credentials are still used for other components beyond backup location.. such as for volume snapshotting if you are using the aws plugin. If you did not add aws plugin then we'll have to check where else this check is occuring. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVDR2MAWYDNCIWWZ2EKOP3UNOVWZANCNFSM5G5H6ISA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Stephen Wilson Senior Storage Consultant Red Hat <https://www.redhat.com/> ***@***.*** M: (601)479-6562 <https://www.redhat.com/>

[kaovilai]

MCG/NooBaa bucket usage currently relies on aws-plugin I believe... at least for our expected support case. How are you using mcg/noobaa without cloud-credentials?

[tkagn]

We are trying to have a BSL per project. We can generate an empty cloud credential to get past this issue.

…

On Tue, Nov 23, 2021 at 11:04 AM Tiger Kaovilai ***@***.***> wrote: MCG/NooBaa bucket usage currently relies on aws-plugin I believe... at least for our expected support case. How are you using mcg/noobaa without cloud-credentials? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVDR2JUTWCGWXYJ2UM4FGDUNO3PVANCNFSM5G5H6ISA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Stephen Wilson Senior Storage Consultant Red Hat <https://www.redhat.com/> ***@***.*** M: (601)479-6562 <https://www.redhat.com/>

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale