Version
pulpcore 3.21.0
pulp_python 3.7.3
Describe the bug
I'm not totally sure I understand what's going on. But it seems like the pulp_python code sets up a remote to fetch the index.html from object storage. Then we hit aiohttp.client_exceptions.ClientConnectorCertificateError. It looks like in doing this aiohttp isn't using the trusted CA for some reason.
It should be noted that the environment is set up properly as I can fetch other content from the distribution such as the wheel files without any ClientConnectorCertificateErrors. These files are stored in Azure storage but obviously fetched via django-storages module. Not sure what the difference is that's causing the ClientConnectorCertificateErrors.
To Reproduce
Set up your pulp instance to use Azure Storage and then upload a package to a repo, distribute it, and then try to install it. I think the workflow from the docs should suffice.
Expected behavior
The package installs.
Version
pulpcore 3.21.0
pulp_python 3.7.3
Describe the bug
I'm not totally sure I understand what's going on. But it seems like the pulp_python code sets up a remote to fetch the index.html from object storage. Then we hit aiohttp.client_exceptions.ClientConnectorCertificateError. It looks like in doing this aiohttp isn't using the trusted CA for some reason.
It should be noted that the environment is set up properly as I can fetch other content from the distribution such as the wheel files without any ClientConnectorCertificateErrors. These files are stored in Azure storage but obviously fetched via django-storages module. Not sure what the difference is that's causing the ClientConnectorCertificateErrors.
To Reproduce
Set up your pulp instance to use Azure Storage and then upload a package to a repo, distribute it, and then try to install it. I think the workflow from the docs should suffice.
Expected behavior
The package installs.