Agree, please file a tracker issue with the info, we'll prioritize
reproducing it.
Cheers,
Matt
On Wed, Dec 5, 2018 at 11:42 AM Florian Haas wrote:
>
> On 05/12/2018 17:35, Maxime Guyot wrote:
> > Hi Florian,
> >
> > Thanks for the help. I did further testing and narrowed it down to
> > objects
On 05/12/2018 17:35, Maxime Guyot wrote:
> Hi Florian,
>
> Thanks for the help. I did further testing and narrowed it down to
> objects that have been uploaded when the bucket has versioning enabled.
> Objects created before that are not affected: all metadata operations
> are still possible.
>
Hi Florian,
Thanks for the help. I did further testing and narrowed it down to objects
that have been uploaded when the bucket has versioning enabled.
Objects created before that are not affected: all metadata operations are
still possible.
Here is a simple way to reproduce this:
On 28/11/2018 19:06, Maxime Guyot wrote:
> Hi Florian,
>
> You assumed correctly, the "test" container (private) was created with
> the "openstack container create test", then I am using the S3 API to
> enable/disable object versioning on it.
> I use the following Python snippet to enable/disable
On Wed, Nov 28, 2018 at 10:07 AM Maxime Guyot wrote:
>
> Hi Florian,
>
> You assumed correctly, the "test" container (private) was created with the
> "openstack container create test", then I am using the S3 API to
> enable/disable object versioning on it.
> I use the following Python snippet
Hi Florian,
You assumed correctly, the "test" container (private) was created with the
"openstack container create test", then I am using the S3 API to
enable/disable object versioning on it.
I use the following Python snippet to enable/disable S3 bucket versioning:
import boto, boto.s3,
On 27/11/2018 20:28, Maxime Guyot wrote:
> Hi,
>
> I'm running into an issue with the RadosGW Swift API when the S3 bucket
> versioning is enabled. It looks like it silently drops any metadata sent
> with the "X-Object-Meta-foo" headerĀ (see example below).
> This is observed on a Luminous 12.2.8
Hi,
I'm running into an issue with the RadosGW Swift API when the S3 bucket
versioning is enabled. It looks like it silently drops any metadata sent
with the "X-Object-Meta-foo" header (see example below).
This is observed on a Luminous 12.2.8 cluster. Is that a normal thing? Am I
misconfiguring