Actions
Backport #17908
closedjewel: rgw: the response element "X-Timestamp" of swift stat bucket api is zero
Release:
jewel
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Updated by Alexey Sheplyakov over 7 years ago
- Copied from Bug #16597: the response element "X-Timestamp" of swift stat bucket api is zero added
Updated by Alexey Sheplyakov over 7 years ago
Updated by Nathan Cutler over 7 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Alexey Sheplyakov
original 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
```
Updated by Nathan Cutler over 7 years ago
- Subject changed from jewel: the response element "X-Timestamp" of swift stat bucket api is zero to jewel: rgw: the response element "X-Timestamp" of swift stat bucket api is zero
Updated by Nathan Cutler about 7 years ago
- Status changed from In Progress to Resolved
- Target version set to v10.2.6
Actions