From: Abhishek Lekshmanan <abhishek@suse.com>
To: Patrick Donnelly <pdonnell@redhat.com>,
Yuri Weinstein <yweinste@redhat.com>
Cc: "Development, Ceph" <ceph-devel@vger.kernel.org>,
"Weil, Sage" <sweil@redhat.com>,
"Durgin, Josh" <jdurgin@redhat.com>,
"Sadeh-Weinraub, Yehuda" <yehuda@redhat.com>,
John Spray <jspray@redhat.com>,
"gmeno@redhat.com" <gregory.meno@inktank.com>
Subject: Re: Status of luminous v12.2.1 integration branch
Date: Fri, 15 Sep 2017 10:54:57 +0200 [thread overview]
Message-ID: <87fubofiji.fsf@suse.com> (raw)
In-Reply-To: <87inglfqsp.fsf@suse.com>
Abhishek Lekshmanan <abhishek@suse.com> writes:
> Patrick Donnelly <pdonnell@redhat.com> writes:
>
>> On Wed, Sep 13, 2017 at 8:49 AM, Patrick Donnelly <pdonnell@redhat.com> wrote:
>>> On Wed, Sep 13, 2017 at 8:40 AM, Yuri Weinstein <yweinste@redhat.com> wrote:
>>>> This email is an attempt to make sure that all are clear on luminous
>>>> v12.2.1 release status.
>>>>
>>>> Dev leads - what is left before we can start QE validation?
>>>
>>> To be merged into master today and then backported:
>>> http://tracker.ceph.com/issues/21378
>>> Luminous backport: http://tracker.ceph.com/issues/21357
>>> To be merged into master today and then backported:
>>> http://tracker.ceph.com/issues/20594
>>
>> Final list of CephFS backports needed for 12.2.1:
>>
>> http://tracker.ceph.com/issues/21323
>> http://tracker.ceph.com/issues/21114
>> http://tracker.ceph.com/issues/21107
>> http://tracker.ceph.com/issues/21357
>> http://tracker.ceph.com/issues/21322
>> http://tracker.ceph.com/issues/21384
>>
>
> So scheduled the relevant suites (rgw,rados,fs) at priority 100 right
> now) for the current PRs targeting Luminous,
> http://tracker.ceph.com/issues/21296#note-15
>
> if this run goes through, lets merge these PRs to luminous and handover
> to Yuri
So had failures in many jobs of all the 3 suites due to an ansible
failure, the fs suite, however, has a few failures in this test
(tasks.cephfs.test_misc.TestMisc), is anyone aware of prior failures of
this suite, can be seen in this run for eg.
http://pulpito.ceph.com/abhi-2017-09-14_11:23:49-fs-wip-luminous-2017-09-14-distro-basic-smithi/1632469/
reruns updated at http://tracker.ceph.com/issues/21296
--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-09-15 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 15:40 Status of luminous v12.2.1 integration branch Yuri Weinstein
2017-09-13 15:43 ` Sage Weil
2017-09-13 15:45 ` Yuri Weinstein
2017-09-14 7:39 ` Orit Wasserman
2017-09-13 15:47 ` Jason Dillaman
2017-09-13 15:49 ` Patrick Donnelly
2017-09-14 4:37 ` Patrick Donnelly
2017-09-14 11:44 ` Abhishek Lekshmanan
2017-09-15 8:54 ` Abhishek Lekshmanan [this message]
2017-09-15 12:04 ` Abhishek Lekshmanan
2017-09-15 17:55 ` Josh Durgin
2017-09-15 18:02 ` Patrick Donnelly
2017-09-15 20:50 ` Abhishek L
2017-09-15 20:51 ` Patrick Donnelly
2017-09-14 11:12 ` Joao Eduardo Luis
[not found] <20890cf9-8e88-45b3-97d2-e6ad5d2ce583@redhat.com>
2017-09-15 21:26 ` Abhishek L
2017-09-15 21:51 ` Yuri Weinstein
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=87fubofiji.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gregory.meno@inktank.com \
--cc=jdurgin@redhat.com \
--cc=jspray@redhat.com \
--cc=pdonnell@redhat.com \
--cc=sweil@redhat.com \
--cc=yehuda@redhat.com \
--cc=yweinste@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.