Bug 1359404
Summary: | [RGW:NFS]:- Timestamp for directories (rgw buckets) which were created before ganesha instantiation is too old | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | shylesh <shmohan> |
Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
Status: | CLOSED ERRATA | QA Contact: | Hemanth Kumar <hyelloji> |
Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | unspecified | ||
Version: | 2.0 | CC: | cbodley, ceph-eng-bugs, hnallurv, kbader, kdreyer, mbenjamin, owasserm, sweil |
Target Milestone: | rc | ||
Target Release: | 2.2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.5-7.el7cp Ubuntu: ceph_10.2.5-3redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Buckets no longer have incorrect time stamps
Previously, buckets created by the Simple Storage Service (S3) API on the Ceph Object Gateway before mounting the Ganesha NFS interface had incorrect time stamps when viewed from NFS. With this update, the NFS service uses time stamps that are based on the correct times of creation or modification of buckets. As a result, buckets created by the S3 API no longer have incorrect time stamps.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-14 15:44:33 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: | 1322504, 1383917, 1412948 |
Description
shylesh
2016-07-23 19:21:58 UTC
Agree, the timestamp for these buckets -should- be an RGW timestamp, not 0. Not sure if this can be changed before 2.1. Matt, what ticket in tracker.ceph.com corresponds to this issue? (In reply to Ken Dreyer (Red Hat) from comment #5) > Matt, what ticket in tracker.ceph.com corresponds to this issue? I've just created http://tracker.ceph.com/issues/17367 for it. Proposed fix in https://github.com/ceph/ceph/pull/11181 Resolved upstream in v10.2.5 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://rhn.redhat.com/errata/RHBA-2017-0514.html |