Bug #7279
closedCapsule/RHEL7 - not picking up cyrus-sasl-plain leads to nonworking capsule
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1134512
Description of problem:
Saw this on fresh capsule install on RHEL7. Might be an issue on RHEL6 too but for some reason I saw the package installed there already - someone else? I know I had to specifically install it myself on RHEL7 though
Version-Release number of selected component (if applicable):
Satellite-6.0.4-RHEL-7-20140823.0
How reproducible:
Steps to Reproduce:
1. Install capsule on RHEL7
2. Note logs and failure to get capsule do anything useful.
Actual results:
lots and lots of messages like
Aug 26 23:14:56 ibm-x3550m3-13 pulp: celery.worker.consumer:ERROR: consumer: Cannot connect to qpid://guest@ibm-x3550m3-13.lab.eng.brq.redhat.com:5671//: Error in sasl_client_start (-4) SASL: no mechanism available: No worthy mechs found.
Upon further investigation, there is no 'cyrus-sasl-plain' package installed.
Expected results:
package installed, working capsule.
Additional info:
- If this is a dupe, we can close it
- Gross workaround:
- yum -y install cyrus-sasl-plain
- service qpidd stop && service pulp_celerybeat stop && service pulp_workers stop && service pulp_resource_manager stop && service httpd stop
- service qpidd start && service pulp_celerybeat start && service pulp_workers start && service pulp_resource_manager start && service httpd start
Updated by Brad Buckingham about 10 years ago
- Assignee set to Brad Buckingham
- Triaged changed from No to Yes
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release set to 86