From: Rishabh Dave Date: Wed, 4 Jun 2025 06:32:54 +0000 (+0530) Subject: release note: add a note that "subvolume info" cmd output can also... X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=37244a7972b9842e3cb8f8ddbd4a1d9ca875bbe3;p=ceph.git release note: add a note that "subvolume info" cmd output can also... contain "source field" in it. Signed-off-by: Rishabh Dave --- diff --git a/PendingReleaseNotes b/PendingReleaseNotes index 8380f6c06e0a..11c013102183 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -140,6 +140,14 @@ allowed. `rbd trash mv` command now behaves the same way as `rbd rm` in this scenario. +* CephFS: If the subvolume name passed to the command `ceph fs subvolume info` + is a clone, the output now will also contain a "source" field that tells user + the name of source snapshot along with the name of volume, subvolume group and + subvolume in which the source snapshot is located. For clones created with + Tentacle or earlier release, the value of this field will be 'N/A'. Regular + subvolumes don't have a source subvolume and therefore the output for them + won't contain a "source" field regardless of the release. + * RGW: Replication policies now validate permissions using `s3:ReplicateObject`, `s3:ReplicateDelete`, and `s3:ReplicateTags` for destination buckets. For source buckets, both `s3:GetObjectVersionForReplication` and `s3:GetObject(Version)`