Bug 1743611

Summary:	RHEL 6 GlusterFS client creates files with time 01/01/1970
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Kotresh HR <khiremat>
Component:	core	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Vinayak Papnoi <vpapnoi>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	nchilaka, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-6.0-13	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 12:22:40 UTC	Type:	---
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:	1696809

Description Kotresh HR 2019-08-20 10:09:50 UTC

This bug was initially created as a copy of Bug #1726175

I am copying this bug because: 



Description of problem:
CentOs 6 gluster client with glusterfs volume mounted creates files with time creation "01/01/1970". Files created by user apache, or with user root with vim, or nano, are created with bad date. But if create with touch, the date is correct. 

Version-Release number of selected component (if applicable):
glusterfs-fuse-6.3-1.el6.x86_64

How reproducible:
Create file in mountpoint with vim, or nano.

Steps to Reproduce:
1. yum install centos-release-gluster6
2. yum install glusterfs-client
3. mount -t glusterfs IP:/remotevol /mnt/localdir
4. cd /mnt/localdir
5. vim asdasdad
6. :wq!
7. ls -lah asdasdad


Actual results:
-rw-r--r--    1 root   root      0 ene  1  1970 test

Expected results:
-rw-r--r--    1 root   root      0 jul  1  2019 test

Comment 10 errata-xmlrpc 2019-10-30 12:22:40 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, 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/RHEA-2019:3249