[Pulp-list] Pulp upgrade from 2.3 to 2.4 issues

[Trevor Vaughan]

I had that exact same issue. Certainly interested in anything that you find
out.

Every attempt that I made at debugging the issue didn't produce much in the
way of results.

Trevor


On Wed, Sep 3, 2014 at 11:47 PM, Mark Keller <mdkeller at gmail.com> wrote:

> Just upgraded my pulp server from 2.3 to 2.4 on CentOS 6. Used the upgrade
> steps and now I can view my repos, but can't update them. Any help would be
> appreciated. I disabled qpid auth per install instructions and ran the ssl
> config script to setup SSL for qpid.
>
> When I run something like the following, I get:
>
> # pulp-admin rpm repo publish run --repo-id myrepo
> +----------------------------------------------------------------------+
>                       Publishing Repository [repo]
> +----------------------------------------------------------------------+
>
> An internal error occurred on the Pulp server:
>
> RequestException: POST request
> on /pulp/api/v2/repositories/cpt/actions/publish/ failed with 500 -
> Unhandled
> Exception
>
>
> Looking through the logs I see the following errors. It seems like the
> pulp clients are still trying to use sasl auth to connect to qpid.
>
> Sep  3 23:34:12 myhost pulp: celery.worker.consumer:ERROR: consumer:
> Cannot connect to qpid://guest@myhost:5671//: Error in sasl_client_start
> (-4) SASL(-4): no mechanism available: No worthy mechs found.
> Sep  3 23:34:12 myhost pulp: celery.worker.consumer:ERROR: Trying again in
> 6.00 seconds...
> Sep  3 23:34:12 myhost pulp: celery.worker.consumer:ERROR:
> Sep  3 23:34:15 myhost python: No worthy mechs found
> Sep  3 23:34:15 myhost pulp: celery.worker.consumer:ERROR: consumer:
> Cannot connect to qpid://guest@myhost:5671//: Error in sasl_client_start
> (-4) SASL(-4): no mechanism available: No worthy mechs found.
> Sep  3 23:34:15 myhost pulp: celery.worker.consumer:ERROR: Trying again in
> 8.00 seconds...
> Sep  3 23:34:15 myhost pulp: celery.worker.consumer:ERROR:
> Sep  3 23:34:15 myhost )    : No worthy mechs found
> Sep  3 23:34:15 myhost )    : No worthy mechs found
> Sep  3 23:34:15 myhost )    : No worthy mechs found
> Sep  3 23:34:15 myhost )    : No worthy mechs found
> Sep  3 23:34:15 myhost python: No worthy mechs found
> Sep  3 23:34:15 myhost pulp: pulp.server.async.scheduler:ERROR: Error in
> sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs
> found
> Sep  3 23:34:15 myhost python: No worthy mechs found
> Sep  3 23:34:15 myhost pulp: celery.beat:ERROR: beat: Connection error:
> Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy
> mechs found. Trying again in 10.0 seconds...
> Sep  3 23:34:15 myhost )    : No worthy mechs found
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR: Error in
> sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs
> found
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR: Traceback (most recent
> call last):
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/pulp/server/webservices/middleware/exception.py",
> line 44, in __call__
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return
> self.app(environ, start_response)
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/pulp/server/webservices/middleware/postponed.py",
> line 42, in __call__
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return
> self.app(environ, start_response)
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/web/application.py", line 279, in wsgi
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     result =
> self.handle_with_processors()
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py",
> line 29, in _handle_with_processors
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return
> process(self.processors)
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py",
> line 26, in process
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return p(lambda:
> process(processors))
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/web/application.py", line 566, in
> processor
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return handler()
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:   File
> "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py",
> line 26, in <lambda>
> Sep  3 23:34:15 myhost pulp:
> pulp.server.webservices.middleware.exception:ERROR:     return p(lambda:
> process(processors))
>
> In /etc/pulp/server.conf I have:
>
> [messaging]
> url: ssl://myhost:5671
> auth_enabled: false
> cacert: /etc/pki/pulp/qpid/ca.crt
> clientcert: /etc/pki/pulp/qpid/client.crt
>
> [tasks]
> broker_url: qpid://myhost:5671/
> celery_require_ssl: true
> cacert: /etc/pki/pulp/qpid/ca.crt
> keyfile: /etc/pki/pulp/qpid/client.crt
> certfile: /etc/pki/pulp/qpid/client.crt
>
> Again, any help appreciated!
>
> Mark
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaughan at onyxpoint.com

-- This account not approved for unencrypted proprietary information --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20140903/3fe09c73/attachment.htm>