All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Bodley <cbodley@redhat.com>
To: Karol Mroz <kmroz@suse.de>, Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: Abhishek Lekshmanan <abhishek@suse.com>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	Sage Weil <sage@newdream.net>,
	Matt Benjamin <mbenjamin@redhat.com>,
	"Dillaman, Jason" <dillaman@redhat.com>,
	Patrick Donnelly <pdonnell@redhat.com>,
	"Durgin, Josh" <jdurgin@redhat.com>
Subject: Re: 12.2.2 status
Date: Fri, 27 Oct 2017 09:57:11 -0400	[thread overview]
Message-ID: <393a5637-16da-2c2f-36ab-334fddc01db1@redhat.com> (raw)
In-Reply-To: <FCD206E6-9E88-478C-9230-D0FAD0F8BA4F@suse.de>



On 10/26/2017 06:48 PM, Karol Mroz wrote:
> +CC Casey
>
> Hi Yehuda and Casey,
>
>
>> On Oct 26, 2017, at 9:50 AM, Yehuda Sadeh-Weinraub <yehuda@redhat.com> wrote:
> […]
>> I'd be happy to see these fixed:
>> http://tracker.ceph.com/issues/21819
> Opened backport ticket http://tracker.ceph.com/issues/21937
> https://github.com/ceph/ceph/pull/18539
>
>
>> http://tracker.ceph.com/issues/21735
> Opened backport ticket http://tracker.ceph.com/issues/21938
> Final commit of https://github.com/ceph/ceph/pull/18198 appears dependent on at least: cbb84cb13db and 53526d5050a in master.  Please advise.

resolved this conflict in https://github.com/ceph/ceph/pull/18591

>> however, these are not in master yet, need validation.
>>
>> This one is ready I think:
>> http://tracker.ceph.com/issues/21500
> Opened: http://tracker.ceph.com/issues/21939
> https://github.com/ceph/ceph/pull/18569
>    - Still need https://github.com/ceph/s3-tests/pull/189 backported to ceph-luminous branch of s3tests

do you want me to cherry-pick that s3test before the backport merges? 
it's likely to cause failures for teuthology runs that don't include 
https://github.com/ceph/ceph/pull/18569

>
> Regards,
> Karol Mroz
> kmroz@suse.de
>
>
>


  reply	other threads:[~2017-10-27 13:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 15:19 12.2.2 status Abhishek Lekshmanan
2017-10-26 15:40 ` Jason Dillaman
2017-10-26 22:38   ` Karol Mroz
2017-10-26 22:42     ` Jason Dillaman
2017-10-27 14:02       ` Jason Dillaman
2017-10-30  8:28         ` kefu chai
2017-10-30 13:09         ` Jason Dillaman
2017-10-26 16:14 ` Sage Weil
2017-10-26 16:47 ` Abhishek Lekshmanan
2017-10-26 16:50 ` Yehuda Sadeh-Weinraub
2017-10-26 22:48   ` Karol Mroz
2017-10-27 13:57     ` Casey Bodley [this message]
2017-10-30 20:38       ` Karol Mroz
2017-10-26 18:05 ` Patrick Donnelly
2017-11-03 17:44   ` Abhishek Lekshmanan
2017-11-03 17:53     ` Sage Weil
2017-11-03 18:02       ` Abhishek Lekshmanan
2017-11-03 20:54         ` kefu chai
2017-11-04  7:51           ` Nathan Cutler
2017-11-05 12:17             ` Abhishek L
2017-11-06  8:52               ` kefu chai
2017-11-06  9:57                 ` Abhishek Lekshmanan
2017-11-06 18:29                   ` Abhishek Lekshmanan
2017-11-06 19:55                     ` Patrick Donnelly
2017-11-07 21:59                       ` Abhishek
2017-11-07 23:09                         ` Patrick Donnelly
2017-11-07 23:51                         ` Matt Benjamin

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=393a5637-16da-2c2f-36ab-334fddc01db1@redhat.com \
    --to=cbodley@redhat.com \
    --cc=abhishek@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=kmroz@suse.de \
    --cc=mbenjamin@redhat.com \
    --cc=pdonnell@redhat.com \
    --cc=sage@newdream.net \
    --cc=yehuda@redhat.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.