-
Notifications
You must be signed in to change notification settings - Fork 193
5.0.3 Regression with SSL handshake #349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@matusvalo would you mind checking this when you have time? |
I host rabbitmq on heroku with a free cloudamqp plugin. |
this is the PR you should be checking #347 |
I will check it... |
Originally posted by @moisesguimaraes in #347 (comment) I think that's the patch that needed to be made before release.. |
Oh, sorry about that. I have the changes stashed here. I'm running the tests locally and will put a PR shortly. |
you could check this fix #350 |
I confirm it works :) |
thanks! |
A recent py-ampq update is causing cachito workers to fail to get local certificates: ``` ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123) ``` This has been reported upstream on celery/py-amqp#349 and fixed on celery/py-amqp#350. However, even with the fix, provided by Fedora on https://bodhi.fedoraproject.org/updates/FEDORA-2021-904397f5c4, Cachito workers still fail to connect to rabbitmq (with the same error) when enforcing SSL connections. Let's pin py-amqp version to the latest version known to work with Cachito so we do not need to halt development/deployments while we deal with the amqp issue. Signed-off-by: Athos Ribeiro <athos@redhat.com>
A recent py-ampq update is causing cachito workers to fail to get local certificates: ``` ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123) ``` This has been reported upstream on celery/py-amqp#349 and fixed on celery/py-amqp#350. However, even with the fix, provided by Fedora on https://bodhi.fedoraproject.org/updates/FEDORA-2021-904397f5c4, Cachito workers still fail to connect to rabbitmq (with the same error) when enforcing SSL connections. Let's pin py-amqp version to the latest version known to work with Cachito so we do not need to halt development/deployments while we deal with the amqp issue. Signed-off-by: Athos Ribeiro <athos@redhat.com>
A recent py-ampq update is causing cachito workers to fail to get local certificates: ``` ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123) ``` This has been reported upstream on celery/py-amqp#349 and fixed on celery/py-amqp#350. However, even with the fix, provided by Fedora on https://bodhi.fedoraproject.org/updates/FEDORA-2021-904397f5c4, Cachito workers still fail to connect to rabbitmq (with the same error) when enforcing SSL connections. Let's pin py-amqp version to the latest version known to work with Cachito so we do not need to halt development/deployments while we deal with the amqp issue. Signed-off-by: Athos Ribeiro <athos@redhat.com>
A recent py-ampq update is causing cachito workers to fail to get local certificates: ``` ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123) ``` This has been reported upstream on celery/py-amqp#349 and fixed on celery/py-amqp#350. However, even with the fix, provided by Fedora on https://bodhi.fedoraproject.org/updates/FEDORA-2021-904397f5c4, Cachito workers still fail to connect to rabbitmq (with the same error) when enforcing SSL connections. Let's pin py-amqp version to the latest version known to work with Cachito so we do not need to halt development/deployments while we deal with the amqp issue. Signed-off-by: Athos Ribeiro <athos@redhat.com>
If I'm not mistaken, kombu is using py-ampq if librabbitmq is not available.
So celery is using kombu which is using py-amqp by default.
No matter what celery version is being used, if py-amqp has no version specified in requirements.txt, the latest one is used.
When I connect to rabbitmq using pika, everything seems to be working fine.
But after installing Celery 5.0.1 or latest commit hash from master, when I do the same with kombu
I get
After adding
amqp==5.0.2
as a dependency everything seems to be working fine.Therefore I conclude that version 5.0.3 comes with some serious regressions.
The text was updated successfully, but these errors were encountered: