Project

General

Profile

Actions

Bug #64182

open

mds: "fs authorize" update MDS caps only if it is last one to be considered

Added by Rishabh Dave 4 months ago. Updated 3 months ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The last two commands have no effect on the caps held by client.x in its keyring -

$ ceph fs volume create b
$ ceph fs authorize a client.x / rw
$ ceph fs authorize a client.x /dir1 rw
$ ceph fs authorize a client.x /dir2 rw
$ ceph auth get client.x
$ ceph fs authorize b client.x / rw
[client.x]
        key = AQAkWrJlNDdPGhAAGHfc3zW2PTJCIdzIJ3aekA==
        caps mds = "allow rw fsname=a, allow rw fsname=a path=dir1, allow rw fsname=a path=dir2, allow rw fsname=b" 
        caps mon = "allow r fsname=a, allow r fsname=b" 
        caps osd = "allow rw tag cephfs data=a, allow rw tag cephfs data=b" 
updated caps for client.x

$ # next two commands will have no effect, last command will print same keyring as above
$ ceph fs authorize b client.x /dir1 rw
no update for caps of client.x
$ ceph fs authorize b client.x /dir2 rw
no update for caps of client.x
$ ceph auth get client.x
[client.x]
        key = AQAkWrJlNDdPGhAAGHfc3zW2PTJCIdzIJ3aekA==
        caps mds = "allow rw fsname=a, allow rw fsname=a path=dir1, allow rw fsname=a path=dir2, allow rw fsname=b" 
        caps mon = "allow r fsname=a, allow r fsname=b" 
        caps osd = "allow rw tag cephfs data=a, allow rw tag cephfs data=b" 

Related issues 1 (0 open1 closed)

Related to CephFS - Feature #47264: "fs authorize" subcommand should work for multiple FSs tooResolvedRishabh Dave

Actions
Actions

Also available in: Atom PDF