Bug 1342259

Summary:	[features/worm] - write FOP should pass for the normal files
Product:	[Community] GlusterFS	Reporter:	Karthik U S <ksubrahm>
Component:	unclassified	Assignee:	Karthik U S <ksubrahm>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, ksubrahm, ndevos, rtalur, sankarshan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1345713 (view as bug list)		Environment:
Last Closed:	2017-03-27 18:13:07 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:	1345713

Description Karthik U S 2016-06-02 19:17:41 UTC

Description of problem:

The write FOP fails for the normal files. It should fail only for WORM or WORM-Retained files.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-06-02 19:44:43 UTC

REVIEW: http://review.gluster.org/14619 (features/worm: fixed issue with write FOP for normal files) posted (#1) for review on master by Karthik U S (ksubrahm)

Comment 2 Vijay Bellur 2016-06-06 10:44:24 UTC

REVIEW: http://review.gluster.org/14619 (features/worm: fixed issue with write FOP for normal files) posted (#2) for review on master by Karthik U S (ksubrahm)

Comment 3 Vijay Bellur 2016-06-13 12:12:54 UTC

COMMIT: http://review.gluster.org/14619 committed in master by Jeff Darcy (jdarcy) 
------
commit 40a7537556a7eb0a7c90ec6e7e2fd4014beae092
Author: karthik-us <ksubrahm>
Date:   Fri Jun 3 01:04:01 2016 +0530

    features/worm: fixed issue with write FOP for normal files
    
    The write FOPs on normal files were being blocked after the recent change.
    It should fail only for the WORM and WORM-Retained files, and should pass
    for a normal file.
    Using auto-commit period to check for dormant files instead of retention period.
    
    Change-Id: I30f82d4de2ea2c59c1eb7b4449ba6a60e568cfd5
    BUG: 1342259
    Signed-off-by: karthik-us <ksubrahm>
    Reviewed-on: http://review.gluster.org/14619
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Manikandan Selvaganesh <mselvaga>

Comment 4 Shyamsundar 2017-03-27 18:13:07 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/