Ceph / Swift cannot disable Object Versioning by sending empty X-Versions-Location header
Bug #1668395 reported by
Rudy McComb
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
MOS Ceph |
Bug Description
Ceph / Swift Cannot Disable Object Versioning.
It seems that ceph or swift is unable to disable object versioning. It appears that this is enabled by default for MOS 9.1, Ceph Hammer. Tried setting this to True then back to False and it still made no difference.
Bug filed on 2/8/17
http://
https:/
Also followed instructions here to verify if object versioning was enabled or disabled.
https:/
Is RGW object versioning hard coded in MOS 9.1 for a reason or is this not its intended outcome.
description: | updated |
Changed in fuel: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → MOS Ceph (mos-ceph) |
milestone: | none → 9.x-updates |
Changed in fuel: | |
status: | Invalid → New |
To post a comment you must log in.
RadosGW in Ceph Hammer doesn't support for Swift API's
object versioning. This feature has been introduced in
Jewel. Thus, marking the bug as invalid.