Description of problem: Customer is using various types of symbolic links. Each one causes geo-replication to go faulty. Version-Release number of selected component (if applicable): How reproducible: Customer encountering faulty geo-replication state being triggered by symbolic links to read-only filesystems. When these sym links are removed, geo-replication is returned to a non-faulty state. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: sh%3A%2F%2Froot%40X.X.X.X%3Agluster%3A%2F%2F127.0.0.1%3Auds-remote.log:OSError: [Errno 30] Read-only file system: '.gfid/dfcdd661-06cb-452d-9c71-c4a6a45ade48' ssh%3A%2F%2Froot%40X.X.X.X%3Agluster%3A%2F%2F127.0.0.1%3Auds-remote.log:OSError: [Errno 30] Read-only file system: '.gfid/be87038f-3faf-4267-86aa-a69194677e5c' ssh%3A%2F%2Froot%40X.X.X.X%3Agluster%3A%2F%2F127.0.0.1%3Auds-remote.log:OSError: [Errno 30] Read-only file system: '.gfid/dfcdd661-06cb-452d-9c71-c4a6a45ade48'
Is this a duplicate of Bug 1565399?
Thank you Kotresh. Considering these issues are indeed the same, I understand that the RCA is outlined upstream at the following URL: https://review.gluster.org/#/c/19872/ Can you please elaborate a bit on this RCA as the customer is requesting more specifics? The customer is concerned that symlinks created last week are OK whereas symlinks created this week are problematic. Also there is concern that a recent upgrade to RHGS 3.3 has triggered this scenario.
have updated the doc text. Kindly review and confirm
Have made the necessary changes.
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/RHSA-2018:2607