Guy Margalit

Hi @arminzqm - You should check for issues in the logs of the operator: `kubectl logs noobaa-operator`. Tnx

@arminzqm great, the last error message says it all...

@tamireran as we discussed this can be fixed manually by creating a backing store with the name `noobaa-default-backing-store`. However this is very manual. We should decide what should be our...

FYI @nb-ohad This is related to the endless reconciles on minikube?

Hi @wudixrw Can you try the `noobaa diagnose` command? Also if you can share this list of namespaced resources: ``` for name in $(kubectl api-resources --verbs=list --namespaced -o name); do...

@bssrikanth Hi. Your case seems to have a different cause then the original - in your case the reason for the installation not advancing is that the noobaa-db PVC is...

Hi @bssrikanth If you use the cli to install noobaa then you should use the following: ``` noobaa install --db-storage-class ibm-spectrum-scale-csi-fileset ``` Otherwise you could manipulate the NooBaa CR ```...

Thanks @aaronmcohen I also thought that this idea would be a good way forward. In the meanwhile we have added the option to provision accounts using CRD/CLI which can be...

In [v2.0.0](https://github.com/noobaa/noobaa-operator/releases/tag/v2.0.0) it was a bit improved so that global resources (storageclass, clusterrole, etc) are assigned a name in the form of .noobaa.io so that it does not mix between...

No sufficient cpu/mem is already detected by [system.CheckWaitingFor()](https://github.com/noobaa/noobaa-operator/blob/ce4e8dacb8d61260c44630d27a2094e0c3419c74/pkg/system/system.go#L444) Need to detect when number of default storage classes is not 1 (0 or 2+ are both a problem).