Bug 1353511

Summary: Renaming a snapshot on Master Node is not getting reflected at Slave Node
Product: Red Hat Ceph Storage Reporter: Tanay Ganguly <tganguly>
Component: RBDAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Tanay Ganguly <tganguly>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0CC: ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, kurs
Target Milestone: rc   
Target Release: 2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.2-22.el7cp Ubuntu: ceph_10.2.2-17redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:43:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tanay Ganguly 2016-07-07 11:01:24 UTC
Description of problem:
Rename the snapshot on Master Node, the renamed snapshot doesn't get reflected on Slave Node.

Version-Release number of selected component (if applicable):
ceph version 10.2.2-15.el7cp

How reproducible:
Always

Steps to Reproduce:
1. Create an Image.
rbd create new/renameq --size 9999 --image-format 2 --image-feature layering,exclusive-lock,object-map,journaling --cluster master

2. Take a snapshot.
rbd snap create new/renameq@latest --cluster master

3. Rename Snapshot
rbd snap rename new/renameq@latest new/renameq@latest-renamed --cluster master
 

Actual results:
New Snapshot name gets reflected in Master Node. But the same is not getting reflected on Slave Node.

Expected results:
On Slave Node also the renamed snapshot should show up.

Additional info:

Comment 4 Jason Dillaman 2016-07-11 22:00:53 UTC
Upstream master branch PR: https://github.com/ceph/ceph/pull/10249

Comment 8 Tanay Ganguly 2016-07-25 09:13:23 UTC
Working Fine, Marking it as Verified.

Comment 10 errata-xmlrpc 2016-08-23 19:43:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1755.html