|
Date: Sun, 04 Oct 2015 22:22:28 +0200
|
|
From: rbarlow@redhat.com
|
|
To: dropbox+pulp+c71e@plan.io
|
|
Message-ID: <56118a8442409_72663fb297069a1c4907f@mercury.mail>
|
|
in-reply-to: redmine.journal-6457.20151002165604.b8eb0d6274ac024e@plan.io
|
|
Subject: Re: [Pulp - Issue #1266] The upgrade from python-kombu-3.0.24-8 to
|
|
python-kombu-3.0.24-9 requires manual intervention from users
|
|
Mime-Version: 1.0
|
|
Content-Type: multipart/mixed;
|
|
boundary=jDUKJ2EIoGvXq0FRr93JS7cmgqkLP50m3;
|
|
charset=UTF-8
|
|
Content-Transfer-Encoding: 7bit
|
|
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
|
|
X-HE-Spam-Level: -----
|
|
X-HE-Spam-Score: -5.0
|
|
X-HE-Spam-Report: Content analysis details: (-5.0 points) pts rule name
|
|
description ---- ----------------------
|
|
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
|
|
Sender listed at http://www.dnswl.org/, high trust [209.132.183.28 listed in
|
|
list.dnswl.org]
|
|
X-HE-SPF: PASSED
|
|
|
|
|
|
--jDUKJ2EIoGvXq0FRr93JS7cmgqkLP50m3
|
|
Content-Type: text/plain;
|
|
charset=UTF-8
|
|
Content-Transfer-Encoding: quoted-printable
|
|
|
|
Pulp wrote:
|
|
> The broker string default in server.conf and config.py are both made
|
|
> with commit d73f4753d9c9a6a2867e12928b214d489081713a
|
|
> <https://github.com/pulp/pulp/commit/d73f4753d9c9a6a2867e12928b214d4890=
|
|
81713a#diff-131aac993b7a876f5b36ffba3ef6c9be>
|
|
> That commit is on 2.6-testing+ (2.6.5). I perceived the "manual step"
|
|
> that the user may need to merge the new server.conf.rpm and their
|
|
> server.conf file if their modified server.conf in some other way. That
|
|
> merging could be unexpected on a Z release.
|
|
> =
|
|
|
|
> Did you not receive that change, and that caused you to experience the
|
|
> issue? What do you think should be done for 2.6.5 in this regard?
|
|
|
|
Given the above, I think you have assuaged my fears as I can probably
|
|
explain what happened to my dev box. I installed my dependencies using
|
|
the beta repository which would have given me this new Kombu, but I was
|
|
developing pulp-docker against Pulp 2.6-release. Thus, I had the new
|
|
Kombu but not the commit you linked above.
|
|
|
|
My only ask at this point is that someone tests to make sure that users
|
|
with a commented broker setting can update from 2.6.4 to 2.6.5 without
|
|
any action. Can we keep this ticket open to track that testing?
|
|
Unfortunately, I will not be available this week to help, but if 2.6.5
|
|
is still not released by next week I can help then.
|
|
|
|
Thanks for the explanation!
|
|
|
|
--jDUKJ2EIoGvXq0FRr93JS7cmgqkLP50m3--
|
.