Closed pcuzner closed 4 years ago
Hello, In noobaa-operator version 2.0.7 or above you can use the diagnose command in the CLI (it should collect all of the relevant logs). In this case, I assume that the problem is within the lib-bucket-provisioner or the noobaa-operator itself. I reckon that a complete noobaa-operator pod log will be sufficient (please attach if possible).
From the log snippet that you've attached, I can conclude the following.
1) I assume that you've deleted the secret (in default namespace) and validated the completion of the operation prior to running the creation. I will validate and check lib-bucket-provisioner's querying and creation of secrets.
I0217 02:52:29.633498 1 resourcehandlers.go:138] "msg"="creating Secret" "key"="default/mybucket" "name"="default/mybucket"
E0217 02:52:29.641754 1 controller.go:286] "msg"="cleaning up reconcile artifacts" "error"="error creating secret for OBC: secrets \"mybucket\" already exists" "key"="default/mybucket
"
I0217 02:52:29.641779 1 controller.go:288] "msg"="deleting storage artifacts" "key"="default/mybucket"
2) The buckets should have been removed as part of the deletion of storage artifacts, but probably failed for this reason or a different reason later on (don't have full log):
E0217 02:52:29.682260 1 controller.go:509] "msg"="error releasing secret" "error"="resource name may not be empty" "key"="default/mybucket"
I0217 02:52:29.682276 1 resourcehandlers.go:182] "msg"="got nil configmap, skipping" "key"="default/mybucket"
I'm attempting to reproduce the problem in order to investigate it (without any success so far). If you have any additional information that can help, please update (full logs, step by step reproduction, access to a system that has this issue). Thank you.
I think the issue related to the sc being misconfigured. After recreating the bucketclass/storageclass OBC's are working correctly!
Thanks for the diagnose command tip!
I have an external ceph cluster (rhcs4), and have created backingstoreclass/storageclass for noobaa - but when I attempt to create an obc I see this in the operator log
so the resource is created, but then immediately deleted. BTW, before I run the oc create, I make sure the mybucket secret doesn't exist!
I'm also confused when I look in the noobaa GUI, since 3 buckets appear with my bucket prefix - but given the above I would expect them to have been cleaned up?
Quite possibly a "user error" - I'm just starting to get a handle on noobaa goodness!
noobaa-operator version : 2.0.10