-
Notifications
You must be signed in to change notification settings - Fork 194
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
Add missing load_default_certs() call. #350
Conversation
Thank you @moisesguimaraes for your PR. Can you also adjust integration tests with case covering this PR? Now they are not failing on master:
|
context.set_ciphers.assert_not_called() | ||
context.verify_mode.assert_not_called() | ||
|
||
context.load_default_certs.assert_called_with( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matusvalo I have tests to cover the new code path already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I saw. But I was curious why integration test creating real tls connection to broker suit does not fail on master. They should fail right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They should only fail when you try to load system certs. I added new tests for this case.
cbc53f5
to
e4f1f1d
Compare
Ok, added some integration tests. |
Our CI is not working, so please check on you repo if they are working fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me but waiting for confirmation
I will check it today. |
OK I have checked the PR and it looks great! Thank you @moisesguimaraes ! I also like the integration test. Thanks again! |
i will try to release tonite or tomorrw morning |
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>
Fixes: #349