All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek@suse.com>
To: Patrick Donnelly <pdonnell@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	Sage Weil <sage@newdream.net>,
	Matt Benjamin <mbenjamin@redhat.com>,
	"Sadeh-Weinraub, Yehuda" <yehuda@redhat.com>,
	"Dillaman, Jason" <dillaman@redhat.com>,
	"Durgin, Josh" <jdurgin@redhat.com>, Karol Mroz <KMroz@suse.com>
Subject: Re: 12.2.2 status
Date: Fri, 03 Nov 2017 18:44:02 +0100	[thread overview]
Message-ID: <874lqbcl5p.fsf@suse.com> (raw)
In-Reply-To: <CA+2bHPYXuma-e-4_XAdLp6rxcT7NBYL+xF4Rz0PAvptLoXvQdw@mail.gmail.com>

Patrick Donnelly <pdonnell@redhat.com> writes:

> On Thu, Oct 26, 2017 at 8:19 AM, Abhishek Lekshmanan <abhishek@suse.com> wrote:
>> Also for the leads, Sage, Yehuda. Jason, Josh, Patrick are there any
>> critical PRs that we need to have in 12.2.2 so that we can include
>> them in the next round of testing before handing over to QE?
>
> Please include:
>
> https://github.com/ceph/ceph/pull/18019
> https://github.com/ceph/ceph/pull/18008

I've added the all the PRs in the milestone with the label wip-abhi-testing,
https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+label%3Awip-abhi-testing

However all the ubuntu/debian tests in teuthology seem to fail with a
dependency issue not seen in centos,

For eg: 
http://pulpito.ceph.com/abhi-2017-11-03_16:49:11-ceph-disk-wip-luminous-backports-distro-basic-vps/

or
http://pulpito.ceph.com/abhi-2017-11-03_15:09:21-rados-wip-luminous-backports-distro-basic-smithi/

something in the lines of
ceph-mds : Depends: ceph-base (= 12.2.1-688-g83b8263-1trusty) but it is
not going to be installed

though not sure why these are failing as the packages themselves seem to
be present at the chacra url, so something else in the dependency chain
somewhere? Has anyone else seen errors of this nature ?


-- 
Abhishek 

  reply	other threads:[~2017-11-03 17:44 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
2017-10-30 20:38       ` Karol Mroz
2017-10-26 18:05 ` Patrick Donnelly
2017-11-03 17:44   ` Abhishek Lekshmanan [this message]
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=874lqbcl5p.fsf@suse.com \
    --to=abhishek@suse.com \
    --cc=KMroz@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jdurgin@redhat.com \
    --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.