Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use Jira Cloud for all bug tracking management.

Bug 1493977

Summary: rbd image-meta set <image-spec> conf_rbd_mirroring_replay_delay <delay in seconds>, delay is not taking effect.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Parikshith <pbyregow>
Component: RBD-MirrorAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: high Docs Contact:
Priority: medium    
Version: 3.0CC: bniver, ceph-eng-bugs, ceph-qe-bugs, hnallurv, pbyregow
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.1-11.el7cp Ubuntu: ceph_12.2.1-13redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:44:47 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:
Embargoed:

Description Parikshith 2017-09-21 09:15:28 UTC 
Description of problem:
Setting replication delay through image metadata on an individual primary image is not taking effect. 

Version-Release number of selected component (if applicable):
12.2.0-2.el7cp

Steps to Reproduce:
1. Create 2 clusters and configure rbd mirroring on them.
2. On primary image set the delay(10mins)
sudo rbd image-meta set data/image-1 conf_rbd_mirroring_replay_delay 600 --cluster master
3. Verify that Image metadata got replicated to a peer(slave) cluster.
sudo rbd image-meta list data/image-1 --cluster slave
There is 1 metadata on this image.
Key                             Value 
conf_rbd_mirroring_replay_delay 600 

4. Write some data on the primary image.

Actual results:
object gets replicated before the delay(almost instantly). 

Expected results:
Replication should start after the delay duration is done.

Additional info:
It works fine if I set the "rbd_mirrorring_replay_delay" configuration option on the slave cluster's rbd-mirror node to configure it globally.
Comment 2 Jason Dillaman 2017-09-24 01:52:58 UTC 
Does this only occur when you set the metadata after the image has been marked for replication? i.e. can you create an image w/ replication disabled, set the configuration option, and enable replication and verify if the delay is handled?
Comment 4 Jason Dillaman 2017-09-25 11:42:53 UTC 
Looks like there are two semi-related issues with the propagation of image-meta values to the non-primary image.
Comment 17 errata-xmlrpc 2017-12-05 23:44:47 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://access.redhat.com/errata/RHBA-2017:3387