-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud credentials secret is not ready
marked as a TemporaryError
but it is not always temporary
#1143
Comments
@dannyzaken |
In 5.11 you can specify a default backingstore spec in NooBaa CR. You can provide a backingstore spec of noobaa-operator/pkg/apis/noobaa/v1alpha1/noobaa_types.go Lines 183 to 184 in 9e4f8e3
Notice that this option will be deprecated in 5.13 and up. in 5.13 there is a boolean flag in noobaa CR |
Environment info
noobaa-operator incorrectly classifies the failure to come up due to
cloud credentials secret "noobaa-aws-cloud-creds-secret" is not ready
as aTemporaryError
. It seems as though noobaa assumes that cloud-credential-operator will always run on all flavors of OpenShift, and that is not the case [*]. In my case, I suspect noobaa isn't supported on ROSA HCP, and soTemporaryError
is misleading.Actual behavior
oc get noobaa -o yaml
Expected behavior
If noobaa hard requires cloud-credentials-operator to be running such that CredentialsRequests are reconciled, the reason should be something more like
UnsupportedPlatform
.Steps to reproduce
noobaa install
on a freshly installed ROSA HCP cluster.Other
Is there a way I can install noobaa-operator without using backing S3 storage? Can I specify that at install time?
[*]
ref1: https://github.com/openshift/cloud-credential-operator#3-manual-credentials-management
ref2: https://github.com/openshift/cloud-credential-operator#4-short-lived-tokens
ref3: https://docs.openshift.com/container-platform/4.13/authentication/managing_cloud_provider_credentials/cco-mode-sts.html
CredentialRequests do not work on OCP STS, ROSA STS, and ROSA HCP clusters.
The text was updated successfully, but these errors were encountered: