Ceph / Swift cannot disable Object Versioning by sending empty X-Versions-Location header

Bug #1668395 reported by Rudy McComb
8
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://tracker.ceph.com/issues/18852
https://github.com/ceph/ceph/pull/13303

Also followed instructions here to verify if object versioning was enabled or disabled.
https://docs.openstack.org/user-guide/cli-swift-set-object-versions.html

Is RGW object versioning hard coded in MOS 9.1 for a reason or is this not its intended outcome.

Rudy McComb (rmccomb)
description: updated
Changed in fuel:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → MOS Ceph (mos-ceph)
milestone: none → 9.x-updates
Revision history for this message
Radoslaw Zarzynski (rzarzynski) wrote :

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.

Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Scott Machtmes (smachtmes) wrote :

So is this information that Mirantis provided not accurate?: https://www.mirantis.com/software/openstack/what-is-new-in-8-0/

Changed in fuel:
status: Invalid → New
Revision history for this message
Kostiantyn Danylov (kdanylov) wrote :

FUEL 8.0 relased with ceph hammer, which does support object versioning via S3 API(not via Swift API) - http://ceph.com/releases/v0-94-hammer-released/. You don't need take any special actions to turn it on, just use standard S3 API.

> So is this information that Mirantis provided not accurate?
Probably S3 need to be mentioned in notes explicitly.

Revision history for this message
Radoslaw Zarzynski (rzarzynski) wrote :

For Ceph Jewel (which isn't in MOS) disabling the Swift's object
versioning is supported with the X-Remove-Versions-Location HTTP
header -- exactly like described in the Swift's documentation [1].

What was not supported is doing that by sending an empty
X-Versions-Location header. However, this is fixed in master now
and the backport process is on the way [2].

I've updated bug titles also in upstream to underline that.

[1] https://docs.openstack.org/developer/swift/overview_object_versioning.html#how-to-disable-object-versioning-in-a-swift-cluster
[2] http://tracker.ceph.com/issues/19176

summary: - Ceph / Swift Cannot Disable Object Versioning
+ Ceph / Swift cannot disable Object Versioning by sending empty
+ X-Versions-Location header
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Won't Fix for 9.x - we won't update Ceph from Hammer to Jewel in MUs for 9.2

Changed in fuel:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.