Bug 1554286
| Summary: | Xattr not updated if increasing the retention of a WORM/Retained file | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | david.spisla |
| Component: | unclassified | Assignee: | Vishal Pandey <vpandey> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-23 04:05:18 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
david.spisla
2018-03-12 10:29:36 UTC
As far as I can tell the purpose of storing ret_period is to restore the file to the original state it had before transitioning into WORM/Retention. If ret_period is not updated correctly then this original state can't ever be restored correctly, which calls into question the whole purpose of storing this value. Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions. REVIEW: https://review.gluster.org/23184 (WIP: xlator update on changing access time of a WORM-Aretained file) posted (#1) for review on master by Vishal Pandey REVIEW: https://review.gluster.org/23184 (Worm: xattr update on changing access time of a WORM-Retained file) merged (#12) on master by Amar Tumballi |