Bug #52131
closedmgr/dashboard: Creation of snapshot for subvol's folder is failing with 500 Internal error
0%
Description
Description of problem:¶
Creation of snapshot for subvol's folder is failing with 500 Internal error
Version-Release number of selected component (if applicable):
ceph version 16.2.0-8.el8cp (f869f8bf2b6e9c3886e94267d378de5d9d57bb61) pacific (stable)
How reproducible:¶
Steps to Reproduce:
1.Create subvol and create a snapshot
2.
3.
Actual results:
Snapshot Creation is failing on subvol's folder
"/volumes/_nogroup/subvol_1/ca90f125-0cdf-4868-b12a-c5c54a1701bf"¶
Expected results:
If it is expected to fail, It should fail with a proper error message.
It would be better if we disable the create snapshot button for these volumes.
If these volumes does not support creation of snapshot
Additional info:¶
[root@ceph-tier0-amar-1624507936499-node7-client ~]# ceph fs subvolume create cephfs subvol_1 --size 5368706371
[root@ceph-tier0-amar-1624507936499-node7-client ~]#
[root@ceph-tier0-amar-1624507936499-node7-client ~]#
[root@ceph-tier0-amar-1624507936499-node7-client ~]# ceph fs subvolume create ^Cphfs subvol_1 --size 5368706371
[root@ceph-tier0-amar-1624507936499-node7-client mnt]# mkdir mount_fs
[root@ceph-tier0-amar-1624507936499-node7-client mnt]# ceph-fuse /mnt/mount_fs/
2021-06-24T04:53:23.382-0400 7fce4b004200 -1 init, newargv = 0x556ee7584ac0 newargc=15
ceph-fuse[22666]: starting ceph client
ceph-fuse[22666]: starting fuse
[root@ceph-tier0-amar-1624507936499-node7-client mnt]# cd /mnt/mount_fs/
[root@ceph-tier0-amar-1624507936499-node7-client mount_fs]# ls -lrt
total 1
drwxr-xr-x. 3 root root 127 Jun 24 04:52 volumes
[root@ceph-tier0-amar-1624507936499-node7-client mount_fs]# cd volumes/_nogroup/subvol_1/
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]# ls -lrt
total 1
drwxr-xr-x. 2 root root 0 Jun 24 04:52 14e107ba-1dca-4bd4-9119-b47dc568ee07
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]# mkdir test
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]# vi test/test_1
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]#
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]# cd 14e107ba-1dca-4bd4-9119-b47dc568ee07/
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# ls -lrt
total 0
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# cp ../test/test_1
cp: missing destination file operand after '../test/test_1'
Try 'cp --help' for more information.
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# cp ../test/test_1 .
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# ls -lrt
total 1
-rw-r--r--. 1 root root 11 Jun 24 04:54 test_1
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# mkdir test
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# ls -lrt
total 1
-rw-r--r--. 1 root root 11 Jun 24 04:54 test_1
drwxr-xr-x. 2 root root 0 Jun 24 04:54 test
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# mkdir .snap/snap_1 --- > inside uuid folder i am not permitted to create it
mkdir: cannot create directory ‘.snap/snap_1’: Operation not permitted
[root@ceph-tier0-amar-1624507936499-node7-client 14e107ba-1dca-4bd4-9119-b47dc568ee07]# cd ..
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]# mkdir .snap/snap_1 -->on subvolume i am able to create it
[root@ceph-tier0-amar-1624507936499-node7-client subvol_1]#
Dashboard should either throw the error saying no permissions or should disable the button
Updated by Pere Díaz Bou over 2 years ago
- Status changed from New to Fix Under Review
- Backport set to pacific
- Pull request ID set to 42732
Updated by Alfonso Martínez over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #52293: pacific: mgr/dashboard: Creation of snapshot for subvol's folder is failing with 500 Internal error added
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".