Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #659

closed

pulp_celerybeat does not start if python-saslwrapper is installed

Added by cduryee almost 10 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
cduryee
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.6 Beta
Platform Release:
2.6.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:

python-saslwrapper is a library that sits on top of sasl. It appears that if this library is installed, we get different errors back from SASL when the "plain" mechanism is not found. This results in python-kombu not skipping the plain mech and trying anonymous, which results in pulp_celerybeat and other services not starting.

Version-Release number of selected component (if applicable): 2.6.0 beta 4, with python-kombu-3.0.24-3.pulp.el7.noarch

How reproducible: every time

Steps to Reproduce:
1. install pulp, and do not set "auth=no" in qpidd.conf
2. install python-saslwrapper
3. attempt to start pulp_celerybeat, log will contain errors
4. yum erase python-saslwrapper and restart pulp_celerybeat, log will not contain errors

Actual results:

lots of errors in pulp log:

celery.beat:ERROR: beat: Connection error: Error in sasl_client_start (-4) SASL (-4): no mechanism available: . Trying again in 32.0 seconds...

This will retry 100 times before attempting to try the ANONYMOUS mechanism.

Expected results:

you should see something like this in the log (normal startup):

kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism ANONYMOUS

+ This bug was cloned from Bugzilla Bug #1182322 +

Actions
Send by e-mail Copy link

Also available in: Atom PDF