Horizon doesn't add mtime for ceph objects
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Won't Fix
|
Medium
|
Alexey Stupnikov | ||
Bug Description
This issue came up after bug #1556874 was fixed. Let me describe its reasons and ways to fix.
Horizon uses x-timestamp or x-object-meta-mtime headers to get modification time displayed in object's information. ceph version used with MOS7.0 doesn't support X-Timestamp and doesn't return it to Horizon; this issue was reported and fixed in bug #1556874 (from now on MOS7 Horizon also uses x-object-meta-mtime to get mtime).
While X-Timestamp will always be in PUT/POST requests (WSGI controller will add it there if none is added by sender), X-Object-Meta-mtime is added only by sender. As a result, Horizon will not add/change mtime and we will get incorrect information displayed.
Steps to reproduce:
1. Deploy MOS7 env with ceph backend. Ensure that patch from bug #1556874 is in the code.
2. Add object from Horizon dashboard.
3. Check object's information, there will be no 'Last Modified' time.
| Changed in mos: | |
| status: | Confirmed → In Progress |
| Alexey Stupnikov (astupnikov) wrote | #1 |
| Alexey Stupnikov (astupnikov) wrote | #2 |
| Alexey Stupnikov (astupnikov) wrote | #3 |
| Changed in mos: | |
| status: | In Progress → Won't Fix |
Patch: https:/