Bucket status give 'INVALID_SCHEMA_REPLY' for all buckets after deleting the account.
See original GitHub issueEnvironment info
[root@api.transcept.cp.fyre.ibm.com ~]# noobaa version INFO[0000] CLI version: 5.9.0 INFO[0000] noobaa-image: noobaa/noobaa-core:5.9.0-20210722 INFO[0000] operator-image: noobaa/noobaa-operator:5.9.0
Openshift Client Version: 4.8.2 Openshift Server Version: 4.8.2 Kubernetes Version: v1.21.1+051ac4f
Actual behavior
- Create a account and use this account key to create buckets.
- Upload the data in the bucket.
- .Delete the account then try to do bucket status of any bucket then it gives INVALID_SCHEMA_REPLY
Expected behavior
- INVALID_SCHEMA_REPLY should not be appear
Steps to reproduce
- Create a account
noobaa api account_api create_account '{
"email": "ketan@noobaa.io",
"name" : "ketan",
"has_login": false,
"s3_access": true,
"allowed_buckets": { "full_permission": true },
"default_resource": "noobaa-s3res-4080029599",
"nsfs_account_config": {
"uid": 1003,
"gid": 1003,
"new_buckets_path": "test2",
"nsfs_only": true
}
}'
- Use Access key to create the bucket.
s3 mb s3://newbucket
- Upload the data
s3 cp /bin/date s3://newbucket
- Delete the account
noobaa api account_api delete_account '{"email":"ketan@ibm.com"}'
- Get the bucket status it gives error.
noobaa bucket status newbucket
INFO[0001] ✅ Exists: NooBaa "noobaa"
INFO[0001] ✅ Exists: Service "noobaa-mgmt"
INFO[0001] ✅ Exists: Secret "noobaa-operator"
INFO[0001] ✅ Exists: Secret "noobaa-admin"
INFO[0001] ✈️ RPC: bucket.read_bucket() Request: {Name:newbucket}
WARN[0001] RPC: GetConnection creating connection to wss://localhost:46433/rpc/ 0xc0001185a0
INFO[0001] RPC: Connecting websocket (0xc0001185a0) &{RPC:0xc00034b090 Address:wss://localhost:46433/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s}
INFO[0001] RPC: Connected websocket (0xc0001185a0) &{RPC:0xc00034b090 Address:wss://localhost:46433/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s}
ERRO[0001] ⚠️ RPC: bucket.read_bucket() Response Error: Code=INVALID_SCHEMA_REPLY Message=INVALID_SCHEMA_REPLY SERVER bucket_api#/methods/read_bucket
FATA[0001] INVALID_SCHEMA_REPLY SERVER bucket_api#/methods/read_bucket
More information - Screenshots / Logs / Other output
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Deleting a bucket - Amazon Simple Storage Service
Make sure the bucket is empty – You can only delete buckets that don't have any objects in them. Make sure the bucket...
Read more >Bucket name seems to still be in use after deleting it
Using the Java S3 SDK, I can create buckets and put objects in them and list contents and delete buckets.
Read more >amazon-s3-developer-guide/delete-or-empty-bucket.md at ...
The following sections provide examples of how to delete a bucket using the AWS SDK ... For buckets without versioning enabled, you can...
Read more >How to Easily Delete an S3 Bucket with Millions of Files in it
I see that the rule has removed 30,222,969 objects since 2/20. I would say give it a few more days and it should...
Read more >Delete buckets | Cloud Storage
This page shows you how to delete Cloud Storage buckets. Important: Once you delete a bucket, anyone can reuse its name for a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@liranmauda , can we have NSFS labelled as well to this one ?
Thank you for the fix. From noobaa side it works.