noobaa-operator
noobaa-operator copied to clipboard
create two namespacestore on same target-bucket with different access-mode
Environment info
- NooBaa Operator Version: 5.13.0
- Platform: Kubernetes v1.22.3
Actual behavior
-
noobaa namespacestore create s3-compatible rw-ns-test --access-mode='read-write' --endpoint='https://objectstore-3.eu-de-2.cloud.sap' --secret-name='s3-secret' --signature-version='v4' --target-bucket='lis.devops.coll-1'
This can be created.
Then I want another namespacestore for readOnly thus
noobaa namespacestore create s3-compatible ro-ns-test --access-mode='read-only' --endpoint='https://objectstore-3.eu-de-2.cloud.sap' --secret-name='s3-secret' --signature-version='v4' --target-bucket='lis.devops.coll-1'
But I am getting
INFO[0000]
INFO[0000] NamespaceStore Wait Ready:
INFO[0000] ⏳ NamespaceStore "ro-ns-test" Phase is "": waiting...
INFO[0003] ⏳ NamespaceStore "ro-ns-test" Phase is "Creating": TemporaryError Target already in use
INFO[0006] ⏳ NamespaceStore "ro-ns-test" Phase is "Creating": TemporaryError Target already in use
INFO[0009] ⏳ NamespaceStore "ro-ns-test" Phase is "Creating": TemporaryError Target already in use
INFO[0012] ⏳ NamespaceStore "ro-ns-test" Phase is "Creating": TemporaryError Target already in use
INFO[0015] ⏳ NamespaceStore "ro-ns-test" Phase is "Creating": TemporaryError Target already in use
i345633 ~ $ noobaa namespacestore list
NAME TYPE TARGET-BUCKET PHASE AGE
ro-ns-test s3-compatible lis.devops.coll-1 Creating 51s
rw-ns-test s3-compatible lis.devops.coll-1 Ready 1m33s
Why this is forbidden? One namespacestore for writing, the other one for reading, i don't see any potential concurrent issue here.