On Wed, Nov 23, 2022, 5:26 PM David Wright <deb...@lionunicorn.co.uk> wrote:
> On Wed 23 Nov 2022 at 20:18:43 (+0100), Nathanael Schweers wrote: > > > It doesn't look like this exact problem is known at > https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue&type=issues, > but there are a few suggestions among the matching bugs. > > > > > One suggestion appears to be that your python module "cryptography" is > too new for Ansible. You don't state how you installed Ansible, but you > might find installing it into a virtualenv is more reliable. > > > > I installed ansible from apt. I therefore wonder how the debian package > > for `python3-cryptography` can be too new for ansible, which is also > > installed via apt, not pip. > > > > I removed the pip installation from my user’s home directory and even > > re-installed all already installed python packages on my system, but I > > still have the same problem. Is this actually broken on debian at the > moment? > > We need to know the versions of the (relevant) packages on your system. > > BTW you started this thread with "I recently installed Debian Bullseye > on my desktop machine, having previously used Debian sid." We need to > know whether the last part of that sentence is of any relevance, or > just an aside. > We also need to know what happened between the "I recently installed Debian" statement and your "suddenly 2 days ago Ansible..." statement. The python runtime messages probably indicate a missing variable. But have you determined that is the actual error? And from where it is missing? Cheers, > David. >
