Bug 1880256 - Geo-rep status going into `Faulty` after the session is started successfully
Summary: Geo-rep status going into `Faulty` after the session is started successfully
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: RHGS 3.5.z Batch Update 3
Assignee: Srijan Sivakumar
QA Contact: Leela Venkaiah Gangavarapu
URL:
Whiteboard:
Depends On:
Blocks: 1874049
TreeView+ depends on / blocked
 
Reported: 2020-09-18 05:46 UTC by Leela Venkaiah Gangavarapu
Modified: 2020-12-17 04:52 UTC (History)
14 users (show)

Fixed In Version: glusterfs-selinux-1.0-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 04:51:53 UTC
Embargoed:
lgangava: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github gluster glusterfs-selinux pull 8 0 None closed Update glusterd.te 2021-02-10 05:26:25 UTC
Red Hat Bugzilla 1889673 0 high CLOSED [RHEL 8] Geo-replication in rsync mode is fails to sync data to the secondary sharded gluster volume 2023-06-27 11:23:22 UTC
Red Hat Product Errata RHBA-2020:5603 0 None None None 2020-12-17 04:52:15 UTC

Comment 26 SATHEESARAN 2020-11-02 10:09:22 UTC 
I have tested with glusterfs-6.0-46.el8rhgs, with volume options set on the primary and secondary volume optimal
for Virtual Machines images store use case. I could observe that all the files are synced to secondary volume
Comment 30 errata-xmlrpc 2020-12-17 04:51:53 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 (glusterfs bug fix and enhancement update), 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-2020:5603
Note You need to log in before you can comment on or make changes to this bug.