Rook and cosi

[Ignazio Cassano]

Hello everyone, I installed rook operetor in my rancher kubernetes cluster using an external ceph s3 cluster and it works fine.

I would like to use così with rook and I installed it but it does not work. Cosi controller receives the bucket claim request and does not report errors but bucket claim remains in not ready status.

Any help, please?

Ignazio

[Mateusz Urbanek]

Hi Ignazio!

Any chance you could share some more details (e.g. logs)?

Regards,

Mateusz

[Ignazio Cassano]

Hi Mateusz, I am out of office but tomorrow I will send you my logs.

But the first question is: by default cosi driver is installed in default namespace like cosi controller.

I remember that logs suggest to move cosi driver under rook-operator namespace.

The second question is: how is the process? Where cosi calls rook? In the documentation I did not find any property where cosi refers rook. So I figure out that cosi is not calling root.

Any case tomorrow I'll share my conf and logs.

Many thanks

Ignazio

--
You received this message because you are subscribed to the Google Groups "container-object-storage-interface-wg" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-object-storage...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/container-object-storage-interface-wg/48ab6072-270b-4881-84b0-2bec25ef95a8n%40googlegroups.com.

[Ignazio Cassano]

If the ceph cosi driver is not installend in rook-operator namespace the rook operator reports reports :

2024-07-29 13:03:46.896589 E | ceph-cosi-controller: failed to reconcile CephCOSIDriver "rook-ceph/ceph-cosi-driver". Ceph COSI Driver namespace must be same as operator

[Ignazio Cassano]

Hi,

compiling the provisioner now I am able to create buckets but not buckeaccess:

the object storage provisioner reports:

I0730 07:23:33.998544       1 provisioner.go:154] Granting user accessPolicy to bucket userNameba-5976d62b-8ca1-42d8-8188-ee65a2c05a09bucketNamesample-bcc1b9302cd-e75a-49c1-a198-588b5e299dbf
E0730 07:23:34.021094       1 provisioner.go:170] "failed to create user" err="BucketNotEmpty tx00000e7c9f27cd7798d60-0066a894f5-4d61a-podto1 4d61a-podto1-podto-ceph"
I0730 07:23:46.831069       1 provisioner.go:154] Granting user accessPolicy to bucket userNameba-5976d62b-8ca1-42d8-8188-ee65a2c05a09bucketNamesample-bcc1b9302cd-e75a-49c1-a198-588b5e299dbf
E0730 07:23:46.851156       1 provisioner.go:170] "failed to create user" err="BucketNotEmpty tx000002c121a7a80c90769-0066a89502-4d61a-podto1 4d61a-podto1-podto-ceph"
I0730 07:24:12.482662       1 provisioner.go:154] Granting user accessPolicy to bucket userNameba-5976d62b-8ca1-42d8-8188-ee65a2c05a09bucketNamesample-bcc1b9302cd-e75a-49c1-a198-588b5e299dbf
E0730 07:24:12.604936       1 provisioner.go:170] "failed to create user" err="BucketNotEmpty tx0000005194424672c6548-0066a8951c-4d61a-podto1 4d61a-podto1-podto-ceph"

Thanks

[Ignazio Cassano]

PS

It created the user and the bucket on my ceph external cluster but it did not create the bucket access

Ignazio

[Blaine Gardner]

I am a Rook maintainer. This issue is specific to Rook and Ceph-COSI driver, so please open an issue with the Rook project at github.com/rook/rook.

Blaine