All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: "Shu, Xinxin" <xinxin.shu@intel.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: rgw errors on the firefly v0.80.10 integration branch
Date: Fri, 08 May 2015 21:16:48 +0200	[thread overview]
Message-ID: <554D0BA0.4010902@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

Hi,

The error we see in the rgw suite at http://tracker.ceph.com/issues/11090#rgw come from http://tracker.ceph.com/issues/11180 which was cherry picked to hammer and giant but not firefly. I cherry picked the relevant commit and ran suites at https://github.com/ceph/ceph-qa-suite/pull/437 and it's all good now. I'm glad I remembered this one, it was a little puzzling the first time around :-)

I think rgw, rbd and fs in http://tracker.ceph.com/issues/11090 can be updated now. Please ping me when it's done and we'll move to the next step :-)

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2015-05-08 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=554D0BA0.4010902@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=xinxin.shu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.