From: Loic Dachary <loic@dachary.org>
To: Alfredo Deza <adeza@redhat.com>, Yuri Weinstein <yweinste@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, John Spray <jspray@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
Abhishek Varshney <abhishek.varshney@flipkart.com>,
"Dachary, Loic" <loic@dachary.org>,
"Just, Samuel" <sjust@redhat.com>,
"Dillaman, Jason" <dillaman@redhat.com>,
David Zafman <dzafman@redhat.com>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: ceph v10.2.3 QE validation status
Date: Tue, 20 Sep 2016 10:45:44 +0200 [thread overview]
Message-ID: <57E0F738.9080706@dachary.org> (raw)
In-Reply-To: <CAC-Np1yDLkQ0OFkroTYXosY8GMvdtX5tW6m5a_9R+eh2Jj1U2A@mail.gmail.com>
On 19/09/2016 22:36, Alfredo Deza wrote:
> On Mon, Sep 19, 2016 at 4:12 PM, Yuri Weinstein <yweinste@redhat.com> wrote:
>> Alfredo, Sage
>>
>> All failed jobs/issues had been addressed/approved (details in
>> http://tracker.ceph.com/issues/16344#note-46) and jewel ceph v10.2.3
>> is ready for release.
> We are unable to cut a release because Jewel is not building on Xenial.
>
> There are issues in the code that creates a virtualenv for
> ceph-disk/ceph-detect-init that uses Python wheels that needs to be
> corrected. Andrew and I have
> been trying to fix this issue on the Jenkins side, but at this point
> we have asked Loic to step in because we haven't been able to get a
> workaround.
>
> See http://tracker.ceph.com/issues/16169
It looks like this is a combo of jenkins providing a machine that is poluted by a previous job and the fact that it does not run install-deps.sh. The discussion continues in the tracker.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
prev parent reply other threads:[~2016-09-20 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 17:12 ceph v10.2.3 QE validation status Yuri Weinstein
2016-09-06 17:27 ` Gregory Farnum
2016-09-06 17:47 ` Ilya Dryomov
2016-09-06 20:19 ` Jason Dillaman
2016-09-06 20:26 ` Yuri Weinstein
2016-09-07 6:33 ` Loic Dachary
2016-09-09 12:41 ` Xiaoxi Chen
2016-09-09 18:19 ` Yuri Weinstein
2016-09-12 20:00 ` Loic Dachary
2016-09-13 16:16 ` Yuri Weinstein
2016-09-15 18:16 ` Sage Weil
2016-09-15 19:54 ` Yuri Weinstein
2016-09-15 20:08 ` Yuri Weinstein
2016-09-19 20:12 ` Yuri Weinstein
2016-09-19 20:36 ` Alfredo Deza
2016-09-20 8:45 ` 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=57E0F738.9080706@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=adeza@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=dzafman@redhat.com \
--cc=jlayton@redhat.com \
--cc=jspray@redhat.com \
--cc=sjust@redhat.com \
--cc=sweil@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox