You can shield yourself from such inadvertent OS changes by using the pip
installation method, preferably with virtual env.
This will also allow you to run any version of ansible.
Dick
On Tue, 29 Oct 2019 at 22:25, Stephen John Smoogen wrote:
> On Tue, 29 Oct 2019 at 17:17, 'Mark Tovey - DSV'
On Tue, 29 Oct 2019 at 17:17, 'Mark Tovey - DSV' via Ansible Project
wrote:
>
>
> So today I ran a playbook on our Ansible server that is still running
> RedHat 7.6 and I saw the issue again. Through experimenting, I finally
> traced it to setting "ANSIBLE_STDOUT_CALLBACK=yaml" before
rkto...@dsv.com | +1 503 222-5546
-Original Message-
From: 'Mark Tovey - DSV' via Ansible Project
Sent: Tuesday, October 29, 2019 8:54 AM
To: ansible-project@googlegroups.com
Subject: RE: [ansible-project] Ansible is totally broken after a OS upgrade
Unfortunately I have already rolle
Subject: Re: [ansible-project] Ansible is totally broken after a OS upgrade
On Mon, 28 Oct 2019 at 16:08, 'Mark Tovey' via Ansible Project
wrote:
>
>
> I just performed a OS upgrade on our Ansible server from RedHat 7.6 to
> RedHat 7.7, and now Ansible has become unusable. When
On Mon, 28 Oct 2019 at 16:08, 'Mark Tovey' via Ansible Project
wrote:
>
>
> I just performed a OS upgrade on our Ansible server from RedHat 7.6 to
> RedHat 7.7, and now Ansible has become unusable. When I try to run any task
> that uses any Ansible fact, I get the following error:
>
>
I just performed a OS upgrade on our Ansible server from RedHat 7.6 to
RedHat 7.7, and now Ansible has become unusable. When I try to run any
task that uses any Ansible fact, I get the following error:
[WARNING]: Failure using method (v2_runner_on_ok) in callback plugin
():
value must
