ceph squid nfs export create uses old keyring format
We recently upgraded from 19.2.3 to 19.2.6. Cluster is deployed with cephadm and I used ceph orch to do the upgrade. I've encountered a small issue with new aes256 keyrings and the 'ceph nfs export create' command. When I disable insecure keyring creation ('ceph config set mon mon_auth_allow_insecure_key false') the nfs export create command fails: ceph nfs export create cephfs --cluster-id clusterid --pseudo-path /test --fsname fsname --path=/test Error EINVAL: Expecting value: line 1 column 1 (char 0) When I set allow insecure key to true and try the command again it creates the export but with an insecure key that generates health warnings on the cluster. The export works fine as far as mounting it and seeing the data I expect. thanks, Ben
[ moving to dev list, bcc ceph-users ] I’m going to guess this means we missed samba as well. Any volunteers, folks? -Greg On Wed, Sep 9, 2026 at 7:53 PM Meekhof, Benjeman <ceph-users@ceph.io> wrote:
We recently upgraded from 19.2.3 to 19.2.6. Cluster is deployed with cephadm and I used ceph orch to do the upgrade. I've encountered a small issue with new aes256 keyrings and the 'ceph nfs export create' command.
When I disable insecure keyring creation ('ceph config set mon mon_auth_allow_insecure_key false') the nfs export create command fails: ceph nfs export create cephfs --cluster-id clusterid --pseudo-path /test --fsname fsname --path=/test Error EINVAL: Expecting value: line 1 column 1 (char 0)
When I set allow insecure key to true and try the command again it creates the export but with an insecure key that generates health warnings on the cluster. The export works fine as far as mounting it and seeing the data I expect.
thanks, Ben
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (2)
-
Gregory Farnum
-
Meekhof, Benjeman