From: Loic Dachary <loic@dachary.org>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rgw backports to giant update
Date: Sat, 31 Jan 2015 00:10:54 +0100 [thread overview]
Message-ID: <54CC0F7E.3060007@dachary.org> (raw)
In-Reply-To: <CABBk=J837H7WnZYBAa=SP0_CcDrRcVzY3_2dB-S_zMk6OHB7XQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2721 bytes --]
Hi Yehuda,
Thanks a lot for this inventory. I updated the tickets to make sure all of them have the "giant" string in the backport field. I'll try backporting myself which will help when it's trivial. If I hit a conflict I'll get back to you :-)
Greetings from Brussels !
On 30/01/2015 20:05, Yehuda Sadeh wrote:
> Hi,
>
> these are the actual issues that I backported:
>
> - 9878 rhel7 s3-tests fail due to missing reason
> - 9918 RGW-Swift: SubUser access permissions, does not seems to workminor
> - 10103 swift tests failing
> - 10354 Failed s3 tests in
> upgrade:dumpling-firefly-x:parallel-next-distro-basic-multi run
> - 10471 rgw: metadata sync doesn't create subusers correctly
> - 9254 rgw: civetweb requires explicit \r\n for http headers
> - 9478 Incorrect content type in response header
> - 9479 ETag is not included in the XML response to put object copy
> operationminor
> - 9877 In some cases it's possible for rgw to segfault on http COPY
> - 10329 rgw: s3 need to return SignatureDoesNotMatch instead of
> AccessDenied- minor
> - 5595 object has a Content-Type, but its content_type property is
> not shown in Swift object enumeration
> - 9907 Normal radosgw-admin: can't disable max_size quota
> - 9973 Validation of Swift DLO manifest object ETag doesn't match
> OpenStack Swift behavior
> - 10307 rgw: setting bucket attributes (swift POST on bucket)
> sometimes failminor
> - 10334 rgw: s3 need to return InvalidAccessKeyId instead of AccessDenied
> - 9587 ceph-radosgw sysvinit script on EL6 cannot set ulimit
>
>
> On Wed, Jan 28, 2015 at 4:48 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Yehuda,
>>
>> Unless I'm mistaken there currently are no rgw issues scheduled to be backported to giant (i.e. with the giant word in the backport field of the issue)[1] that have already been backported to firefly, as part of the v0.80.8[2] release or after[3]. You mentionned that about 18 patches backported to firefly should also be backported to giant and I was hoping to find which one exactly thanks to the backport field.
>>
>> I'll go thru the rgw backports found in v0.80.8 to figure out which one should be in giant. I don't need anything righ now, this is just an update to let you know things are making progress.
>>
>> Cheers
>>
>> [1] inventory of the pending giant v0.87.1 release http://tracker.ceph.com/issues/10501
>> [2] inventory of the firefly v0.80.8 commits http://tracker.ceph.com/issues/10639
>> [3] inventory of the pending firefly v0.80.9 release http://tracker.ceph.com/issues/10641
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>
>>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-01-30 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 0:48 rgw backports to giant update Loic Dachary
2015-01-30 19:05 ` Yehuda Sadeh
2015-01-30 23:10 ` Loic Dachary [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54CC0F7E.3060007@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=yehuda@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox