Bug 1117010
Summary: | Geo-rep: No cleanup for "CHANGELOG" files at bricks from master and slave volumes. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | vnosov <vnosov> |
Component: | geo-replication | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.1 | CC: | avishwan, bugs, gluster-bugs, vnosov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-30 05:33:25 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
vnosov
2014-07-07 19:44:06 UTC
In the latest release of Gluster(3.7), Changelogs are generated only when there are some changes. Generation of Empty Changelogs disabled. Do we need this enhancement to be backported to 3.5.x? We can close this bug if enhancement not required for 3.5.x. Aravinda, I'm using 3.6.X and 3.7.X now. So it's OK not to backport fix to 3.5.X. Thanks! BZ 1208470 fixes this issue by not generating Changelogs in Gluster 3.7. Closing this bug based on Comment 2. Please reopen if required again in 3.5.x version. Thanks. |