release note: add a note that "subvolume info" cmd output can also...

contain "source field" in it.

Resolves: rhbz#2349154
Signed-off-by: Rishabh Dave <ridave@redhat.com>
(cherry picked from commit 37244a7972b9842e3cb8f8ddbd4a1d9ca875bbe3)
(cherry picked from commit 7339f4e45f97cf2ee568a270cc395226f0c8da1c)

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 0be5cf2669ab10246b9aef389f2d8e7aa668696e..58d1bef9d03dc0025a918b4434d22c9f7fbbd21a 100644 (file)
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -152,6 +152,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)`