All of lore.kernel.org
 help / color / mirror / Atom feed
From: kefu chai <tchaikov@gmail.com>
To: Abhishek L <abhishek.lekshmanan@gmail.com>
Cc: Nathan Cutler <ncutler@suse.cz>, Kefu Chai <kchai@redhat.com>,
	Abhishek Lekshmanan <abhishek@suse.com>,
	vumrao@redhat.com, Sage Weil <sweil@redhat.com>,
	Nathan Cutler <NCutler@suse.com>,
	"Dreyer, Ken" <kdreyer@redhat.com>,
	Patrick Donnelly <pdonnell@redhat.com>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	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: Mon, 6 Nov 2017 16:52:08 +0800	[thread overview]
Message-ID: <CAJE9aOP+11MR+kKDKiCQx4FQPjofBkQcecEFOJjubZX30br-Og@mail.gmail.com> (raw)
In-Reply-To: <CAEw75dMUFUQ5JAd4LRX=ycjo0d0C7RmvqMq6d+=5qkKcaGf8ow@mail.gmail.com>

On Sun, Nov 5, 2017 at 8:17 PM, Abhishek L
<abhishek.lekshmanan@gmail.com> wrote:
> On Sat, Nov 4, 2017 at 8:51 AM, Nathan Cutler <ncutler@suse.cz> wrote:
>>> all or nothing. if we want to backport the fix of
>>> http://tracker.ceph.com/issues/21762, we will have to backport the
>>> "debian: fix package relationships after" fixes. so i think pull/18589
>>> is self-contained. and no additional step is needed.
>>>
>>> and per http://tracker.ceph.com/issues/21762, we need to have it in
>>> luminous. but i have no strong opinion on including it in 12.2.2 or
>>> post 12.2.2. Vikhyat and Nathan, what do you think?
>>
>>
>> Yes, I tried to make 18589 self-contained by pulling in Kefu's and
>> Abhishek's follow-on fixes. I think it would be nice to have it in 12.2.2.
>
> Rebuilt the integration branch with the newer PR and it still fails
> with the same reason
> http://pulpito.ceph.com/abhi-2017-11-05_11:53:02-ceph-disk-wip-abhi-testing-2017-11-05-0933-distro-basic-vps/
> for eg.
>
> Kefu, are there any more commits we need to solve the dependency issue?

well, yes and no.

we need to "dch" the changelog, to bump up the version number to
12.2.2 to address this issue. but i thought this was a step of our
release process: see
https://github.com/ceph/ceph-build/blob/2cb4f4069c7a0fac1abecd76e6014272f22cf139/ansible/roles/ceph-release/tasks/release/stable.yml#L3.

that's why i believed that PR#18589 was self-contained. anyway, we can
"fix" this issue in two ways:

1. "dch" the changelog in a commit only for testing, and it will not
be merged into luminous. run that the upgrade suites using dch'ed
version, and wait until the jenkins builder to tag and dch
automatically for the official release of 12.2.2
2. just drop the PR#18589. so and include it in post 12.2.2. so the
problem will be resolved w/o any efforts by then.


-- 
Regards
Kefu Chai

  reply	other threads:[~2017-11-06  8:52 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
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 [this message]
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=CAJE9aOP+11MR+kKDKiCQx4FQPjofBkQcecEFOJjubZX30br-Og@mail.gmail.com \
    --to=tchaikov@gmail.com \
    --cc=KMroz@suse.com \
    --cc=NCutler@suse.com \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=abhishek@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=kchai@redhat.com \
    --cc=kdreyer@redhat.com \
    --cc=mbenjamin@redhat.com \
    --cc=ncutler@suse.cz \
    --cc=pdonnell@redhat.com \
    --cc=sweil@redhat.com \
    --cc=vumrao@redhat.com \
    --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.