[GitHub] [couchdb] skeyby commented on issue #1611: Bad Security Object Error After Moving Shards

[GitBox <gi...@apache.org>]

skeyby commented on issue #1611:
URL: https://github.com/apache/couchdb/issues/1611#issuecomment-666300740


   Hello, I'm facing the same issue on CouchDB 3.1:
   
   `[error] 2020-07-30T10:47:23.718632Z couchdb@10.133.136.126 <0.23319.995> -------- Bad security object in <<"_users">>: [{{[{<<"members">>,{[{<<"roles">>,[<<"_admin">>]}]}},{<<"admins">>,{[{<<"roles">>,[<<"_admin">>]}]}}]},8},{{[{<<"admins">>,{[{<<"roles">>,[<<"_admin">>]}]}}]},8}]
   `
   
   This is the path I followed:
   - I added a new node to the cluster
   - I added all the shards/nodes to the metadata for the db
   - I invoked _sync_shards for the database
   
   The shards correctly appeared on the other node but the security object got lost and the error started to appear in the log.
   
   I went in the db with Fauxton and the permission were back to basic _admin/_admin.
   
   I modified them and the error has now gone away.
   
   So my guess is that there's something missing in the _sync_shards code when it comes to copying database permissions.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org