Tried the python virtualenv and downgrading/upgrading all the possible
packages with no success.
But I finally resolved the issue after mingling with the system packages...
I'm running python 2.7.12 and the issue for me was, that the libs
*python3-crypto* & *python3-cffi-backend* were
I would say a faster way is probably to setup a python virtualenv and see
if you can reproduce the issue in the new clean virtual env.
You can find instructions how to setup a python virutal env
at https://docs.python-guide.org/dev/virtualenvs/
On Tuesday, August 14, 2018 at 11:40:04 AM UTC-7,
The current stable ansible version is 2.6.2 according to the github release
page https://github.com/ansible/ansible/releases
How did you get Ansible version 2.7.0? is the from the devel branch?
On Tuesday, August 14, 2018 at 9:24:15 AM UTC-7, Vid Jelen wrote:
>
> My current python cryptography
I think the upgrade brought in at least 25 updated packages, so it might be
a bit messy to revert each & every one :/
But I'll have a go at it and see what I can find from there.
On Tue, Aug 14, 2018 at 7:09 PM Dick Visser wrote:
> Hmm, that sounds like a somewhat volatile environment.
> In
Hmm, that sounds like a somewhat volatile environment.
In any case, if somethings "suddenly" stops working, I would suggest
to find out what exactly changed that caused it to stop working.
Carpet-upgrading involved libraries might fix the issue, but it's not
going to make fault finding easier.
My current python cryptography version is 2.3 & I've also upgraded pip
itself via pip to 18.0
Ansible version is 2.7.0
I have tried reinstalling python cryptography several times with no
different results than the same error message.
The paramiko package also crossed my mind, so I updated that
Having just looked into this issue as it related to paramiko, the problem
is with having an outdated version of python cryptography installed.
On Tue, Aug 14, 2018 at 10:56 AM Dick Visser wrote:
> On 14 August 2018 at 15:35, wrote:
> >
> > Had a functional ansible-vault setup up until today.
On 14 August 2018 at 15:35, wrote:
>
> Had a functional ansible-vault setup up until today.
Without going into details - what changed on your system today?
Because logic dictates that ansible-vault (or any other tool, for that
matter) doesn't stop working if nothing changed.
Dick
--
You
Had a functional ansible-vault setup up until today.
With each run now I get the following:
*ERROR! Unexpected Exception, this is probably a bug: from_buffer() cannot
return the address of the raw string within a str or unicode or bytearray
object*
This is a known bug and I have tried
