IBM Support

NooBaa OBC creation fails with error bucket already exists

Troubleshooting


Problem

  • NooBaa OBC creation fails with the error "bucket already exists" when bucketclass is configured as Namespace store nsfs-store
  • Multiple OBC creations fail using the same bucketclass when it is configured with Namespace store nsfs-store.

Cause

When bucketclass is configured using namespace store, there is a restriction on namespace buckets, two different buckets cannot point to the same path in the filesystem. 

Environment

IBM Storage Fusion Data Foundation 4.x
Red Hat OpenShift Data Foundation 4.x

Diagnosing The Problem

The following logs can be observed in noobaa-operator logs. 
I0828 07:09:36.671898       1 controller.go:406] "msg"="provisioning" "bucket"="bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409" "key"="openshift-storage/bucket2"
time="2025-08-28T07:09:36Z" level=info msg="Provision: got request to provision bucket \"bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409\"" provisioner=openshift-storage.noobaa.io/obc
time="2025-08-28T07:09:36Z" level=info msg="✅ Exists: NooBaa \"noobaa\"\n"
time="2025-08-28T07:09:36Z" level=info msg="✅ Exists: Service \"noobaa-mgmt\"\n"
time="2025-08-28T07:09:36Z" level=info msg="✅ Exists: Secret \"noobaa-operator\"\n"
time="2025-08-28T07:09:36Z" level=info msg="✅ Exists: Secret \"noobaa-admin\"\n"
time="2025-08-28T07:09:36Z" level=info msg="✅ Exists: BucketClass \"vadeshpa\"\n"
time="2025-08-28T07:09:36Z" level=info msg="✈️  RPC: bucket.read_bucket() Request: {Name:bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409}"
time="2025-08-28T07:09:36Z" level=error msg="⚠️  RPC: bucket.read_bucket() Response Error: Code=NO_SUCH_BUCKET Message=No such bucket: bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409"
time="2025-08-28T07:09:36Z" level=info msg="Provisioner: replication policy " provisioner=openshift-storage.noobaa.io/obc
time="2025-08-28T07:09:36Z" level=info msg="creating namespace bucket info stucture {Type:Single Single:0xc001ec2250 Multi:<nil> Cache:<nil>} from namespace policy"
time="2025-08-28T07:09:36Z" level=info msg="created namespace bucket info stucture successfully &{WriteResource:{Resource:vadeshpa Path:} ReadResources:[{Resource:vadeshpa Path:}] Caching:<nil>} "
time="2025-08-28T07:09:36Z" level=info msg="✈️  RPC: bucket.create_bucket() Request: {Name:bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409 Tiering: ForceMd5Etag:<nil> BucketClaim:0xc001a36c00 Namespace:0xc0011ee840 Quota:<nil>}"
time="2025-08-28T07:09:36Z" level=error msg="⚠️  RPC: bucket.create_bucket() Response Error: Code=BUCKET_ALREADY_EXISTS Message=BUCKET_ALREADY_EXISTS"
time="2025-08-28T07:09:36Z" level=error msg="Bucket \"bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409\" already exists" provisioner=openshift-storage.noobaa.io/obc
E0828 07:09:36.694217       1 controller.go:205] error syncing 'openshift-storage/bucket2': error provisioning bucket: Bucket "bucket2-aa9841d5-8b3b-4b93-9c38-381bca7bd409" already exists, requeuing
time="2025-08-28T07:09:40Z" level=info msg="RPC Handle: {Op: req, API: server_inter_process_api, Method: update_master_change, Error: <nil>, Params: map[is_master:true]}"

Resolving The Problem

There are two workarounds that can be followed.
  • We can create new Namespace store and bucketclass and then provision new OBC from new bucketclass.

  • Create OBC using CLI and mention the "path" value under the "additionalConfig" in obc.yaml. This will define the subdir in the root filesystem to store the bucket's data. e.g.:

    $ cat obc.yaml
apiVersion: objectbucket.io/v1alpha1
kind: ObjectBucketClaim
metadata:
  name: bucket-test2
spec:
  additionalConfig:
    bucketclass: vadeshpa
    path: 'bucket-test2'
  generateBucketName: bucket-test2
  storageClassName: openshift-storage.noobaa.io

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSSEWFV","label":"Storage Fusion Data Foundation"},"ARM Category":[{"code":"a8m3p000000UoIPAA0","label":"Support Reference Guide"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Document Information

Modified date:
01 September 2025

UID

ibm17243540

Page Feedback