Hello Alexander, On Wed, Sep 1, 2021 at 3:29 AM Kiotsoukis, Alexander <a.kiotsoukis@xxxxxxxxxxxxx> wrote: > > Hi all, > > when I first tested and documented ceph fs mounts in VMs, I used the command > > ceph fs authorize filesystem client.kio /kio rw > > This adds "tag cephfs data=filesystem" to the osd caps. > > [client.kio] > key = AQAkuihh/0wcMRAAA5ITjv64XseOJuVWb41scA== > caps mds = "allow rw path=/kio" > caps mon = "allow r" > caps osd = "allow rw tag cephfs data=filesystem " > > We now wanted to use ceph fs mount in a developer VM. It turned out, that in one of the last updates the functionality changed. The tag now prohibits writing in files in the mounted directory. To be able to fully access the mount, I have to use > > ceph auth get-or-create client.kio mds "allow rw path=/kio" mon "allow r" osd "allow rw tag cephfs data=filesystem" > > Ist hat a bug or is that an intended behaviour change? I'm not seeing a difference between the caps produced by `fs authorize` and your `auth get-or-create`? -- Patrick Donnelly, Ph.D. He / Him / His Principal Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |