[Pulp-list] Pulp upgrade from 2.3 to 2.4 issues
bbouters at redhat.com
Mon Nov 24 22:18:08 UTC 2014
Setting auth=no in qpidd.conf and restarting Qpid will disable SASL auth for Qpid, and also makes for an insecure installation. The default broker string that Pulp uses to connect to Qpid does not attempt to use auth, and will connect to a Qpid instance that has authentication disabled. Mark received the SASL error so his Qpid environment is still expecting auth.
If you set a setting in qpidd.conf you're changing the behavior or Qpid, not Pulp. They need to be configured to work together. Hopefully this is helpful.
----- Original Message -----
> From: "Steven Roberts" <strobert at strobe.net>
> To: "Brian Bouterse" <bbouters at redhat.com>
> Cc: "Mark Keller" <mdkeller at gmail.com>, pulp-list at redhat.com
> Sent: Monday, November 24, 2014 2:00:15 AM
> Subject: Re: [Pulp-list] Pulp upgrade from 2.3 to 2.4 issues
> On Thu, Sep 04, 2014 at 05:38:16AM -0400, Brian Bouterse wrote:
> > Hi Mark,
> > This exception is caused by an authentication error with Qpid. I
> > believe you're missing a package that provides the Cyrus SASL
> > authentication type. This results in the "SASL(-4): no mechanism
> > available: No worthy mechs found" message. I recommend installing
> > cyrus-sasl-plain package, and restarting qpidd, httpd,
> > pulp_celerybeat, pulp_workers, and pulp_resource_manager. Then try it
> > again. We have a BZ on this as a known issue .
> > : https://bugzilla.redhat.com/show_bug.cgi?id=1099954
> > -Brian
> if I set auth=no in qpidd.conf pulp shouldn't be using sasl right?
> or am I missing something?
> the docs say pulp is not expecting auth by default, but this error
> sounds like it might be.
> I am trying to run a 'pulp-admin rpm repo sync run'
More information about the Pulp-list