|
Date: Fri, 02 Oct 2015 18:49:11 +0200
|
|
From: rbarlow@redhat.com
|
|
To: dropbox+pulp+c71e@plan.io
|
|
Message-ID: <560eb5875b329_5c243f83910d9a1830217@mercury.mail>
|
|
in-reply-to: redmine.journal-6455.20151002163222.2faffb80588ac6ac@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=WOOja8SS5qxv99cgnu5SjWG5frm3MWXUT;
|
|
charset=UTF-8
|
|
Content-Transfer-Encoding: 7bit
|
|
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
|
|
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
|
|
|
|
|
|
--WOOja8SS5qxv99cgnu5SjWG5frm3MWXUT
|
|
Content-Type: text/plain;
|
|
charset=UTF-8
|
|
Content-Transfer-Encoding: quoted-printable
|
|
|
|
Pulp wrote:
|
|
> It is correct that the 3.0.24-9 release of kombu does require the
|
|
> server.conf broker string to be adjusted. We can revert the upgrade of
|
|
> kombu to the 3.0.24-9 from the 2.6.X release stream and leave the
|
|
> requirement to update the server.conf to a 2.7.0 upgrade. The downside
|
|
> is that 2.6.X will have a known deadlock because the broker string
|
|
> default in 2.6.X isn't safe and causes deadlock with SASL PLAIN
|
|
> low-level libraries prompting on stdin. Given that, do you think we
|
|
> should have the user modify their server.conf with 2.7.0 or 2.6.4? I'm
|
|
> ok with it either way.
|
|
|
|
Can we not simply adjust the default in config.py (and also in the
|
|
server.conf template) so that upgrading users do not need to do anything?=
|
|
|
|
|
|
--WOOja8SS5qxv99cgnu5SjWG5frm3MWXUT--
|
.