Project

General

Profile

Actions

Bug #16597

closed

the response element "X-Timestamp" of swift stat bucket api is zero

Added by wei qiaomiao almost 8 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

when we get the stat of a bucket with swift stat bucket api, the response element "X-Timestamp" is zero, i.e.

```
[root@c7 weiqm]# swift stat my-bucket-3
Account: v1
Container: my-bucket-3
Objects: 0
Bytes: 0
Read ACL:
Write ACL:
Sync To:
Sync Key:
Accept-Ranges: bytes
X-Storage-Policy: default-placement
X-Container-Bytes-Used-Actual: 0
X-Timestamp: 0.00000
X-Trans-Id: tx00000000000000000000f-00577a3762-31d43-default
Content-Type: text/plain; charset=utf-8
```


Related issues 1 (0 open1 closed)

Copied to rgw - Backport #17908: jewel: rgw: the response element "X-Timestamp" of swift stat bucket api is zeroResolvedAlexey SheplyakovActions
Actions #2

Updated by Alexey Sheplyakov over 7 years ago

  • Copied to Backport #17908: jewel: rgw: the response element "X-Timestamp" of swift stat bucket api is zero added
Actions #3

Updated by Loïc Dachary over 7 years ago

  • Status changed from New to Pending Backport
  • Backport set to jewel
Actions #4

Updated by Nathan Cutler about 7 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF