Bug 1498391
Summary: | [RFE] Changelog option in a gluster volume disables with no warning | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rochelle <rallan> | |
Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
Status: | CLOSED ERRATA | QA Contact: | Rochelle <rallan> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.3 | CC: | amukherj, csaba, khiremat, rallan, rhinduja, rhs-bugs, sheggodu, srmukher, storage-qa-internal | |
Target Milestone: | --- | Keywords: | FutureFeature | |
Target Release: | RHGS 3.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.2-2 | Doc Type: | Enhancement | |
Doc Text: |
Geo-replication uses changelog feature and enables it as part of geo-rep session creation. But the command to disable changelog doesn't warn about geo-replication being configured and disabled successfully. With this fix, a check is added while disabling changelog to check for a geo-replication session. Hence, while disabling changelog, a warning is generated for the user about an existing geo-replication session(if any).
|
Story Points: | --- | |
Clone Of: | ||||
: | 1503227 (view as bug list) | Environment: | ||
Last Closed: | 2018-09-04 06:36:24 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1503132, 1503227 |
Description
Rochelle
2017-10-04 08:12:24 UTC
Hi Rochelle, Before fixing this, let's get to know how does it affect geo-replication. I think geo-replication should go to hybrid crawl if the changelogs are not available and would affect unlinks and rename syncing. @Rochelle, Could you confirm this? Upstream Patch: https://review.gluster.org/#/c/18540/ (master) Have updated the doc text. kindly review and confirm the technical accuracy for the same. 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 |