noobaa-core: Bucket status give 'INVALID_SCHEMA_REPLY' for all buckets after deleting the account.

Environment 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

  1. Create a account and use this account key to create buckets.
  2. Upload the data in the bucket.
  3. .Delete the account then try to do bucket status of any bucket then it gives INVALID_SCHEMA_REPLY

Expected behavior

  1. INVALID_SCHEMA_REPLY should not be appear

Steps to reproduce

  1. 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
   }
 }'
  1. Use Access key to create the bucket.
s3 mb s3://newbucket
  1. Upload the data
s3 cp /bin/date s3://newbucket
  1. Delete the account
 noobaa api account_api delete_account '{"email":"ketan@ibm.com"}'
  1. 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

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (8 by maintainers)

Most upvoted comments

@liranmauda , can we have NSFS labelled as well to this one ?