This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1479673 - [rbd-mirror] - Unable to write data on the promoted image from secondary rbd host
[rbd-mirror] - Unable to write data on the promoted image from secondary rbd ...
Status: VERIFIED
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RBD-Mirror (Show other bugs)
3.0
Unspecified Unspecified
medium Severity medium
: rc
: 3.0
Assigned To: Jason Dillaman
Parikshith
Bara Ancincova
:
Depends On:
Blocks: 1494421
  Show dependency treegraph
 
Reported: 2017-08-09 03:09 EDT by Harish NV Rao
Modified: 2017-10-20 11:09 EDT (History)
5 users (show)

See Also:
Fixed In Version: RHEL: ceph-12.1.4-1.el7cp Ubuntu: ceph_12.1.4-2redhat1xenial
Doc Type: Bug Fix
Doc Text:
.Restarting `rbd-mirror` is no longer required after a non-orderly shutdown In RBD mirroring configuration, the local non-primary images could not be force promoted after a non-orderly shutdown of the remote cluster. Consequently, if this happened, and the `rbd-mirror` daemon was not restarted on the local cluster, it was not possible to promote the image because the `rbd-mirror` did not release the exclusive lock. This bug has been fixed, and restarting `rbd-mirror` is no longer required in this case.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Harish NV Rao 2017-08-09 03:09:57 EDT
Description of problem:

Unable to write data on the promoted image from secondary rbd host 

creating this bz in 3.0 as per https://bugzilla.redhat.com/show_bug.cgi?id=1365648#c47


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1) Configured mirroring for a newly created image.
2) Performed some I/O's and Turned off all primary cluster machines abruptly.
3) Performed forceful promotion of images in remote cluster using argument '--force'.
4) Tried to perform I/Os on images from remote clusters. Did not work.
5) Tried the worked around -> Restarting the mirroring service - It worked out as expected.

Actual results:
Unable to perform I/Os on images from remote clusters.

Expected results:
Able to perform I/Os on images from remote clusters.

Additional info:
Workaround: Restarting the mirroring service

Note You need to log in before you can comment on or make changes to this bug.