Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

> On 10/14/2021 3:05 PM Sandip Bhattacharya  wrote:
>
> Can you do:
> ansible [hostname] -m setup

yes, that works

> On 10/14/2021 Jean-Yves LENHOF wrote:
> 
> Did you surcharge the python interpreter variable in a config file ? 
(/etc/ansible.cfg, ~/.ansible.cfg, etc...)

I had a similar idea nad see an 'interpreter_ansible=auto_silent' in my 
effective ansible.cfg- Turning that off does not change anything though


> On 10/14/2021 Racke wrote:
> 
> Somewhere the value /usr/bin/python3 must come from ... try to grep for this 
> string through all relevant directories.

tadaaa! there was a interpreter_python=/usr/bin/python3 in a vars_file 
effective for that playbook which I wasn't aware off. changing that and this 
particular problem goes away.

thank you everybody for your input

... I am hanging on the next task now, but that's a different story

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1414320242.100674.1634218256024%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[Sandip Bhattacharya]

On 14.10.21 14:03, dulhaver via Ansible Project wrote:

On 10/14/2021 1:41 PM dulhaver via Ansible Project 
 wrote:

  
also I can run ad-hoc commands (like ping) on that target successfully (which should proove to some extend that python can be addressed on target, shouldn't it?)


this i.e. also works

ansible [hostname] -m shell -a 'yum install @postgresql -y' --become



Can you do:
   ansible [hostname] -m setup

--
https://blog.sandipb.net
https://twitter.com/sandipb

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/7ca43bae-7ca4-89aa-c1ec-a08e7ed0846f%40showmethesource.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

['Jean-Yves LENHOF' via Ansible Project]

Le 2021-10-14 14:14, dulhaver via Ansible Project a écrit :
On 10/14/2021 1:44 PM Sandip Bhattacharya 
 wrote:



On 14.10.21 11:49, dulhaver via Ansible Project wrote:
> I am running a playbook to install postgresql  
against a centos7 (python 2.75) target and am getting this error about a bad python 
interpreter .
>
> I try to solve this via the inventory.yml
>
> all:
>    hosts:
>      [hostname]: # centos7

Is this literally what is in your inventory.yaml file? Is that even 
valid yaml?

Shouldn't it be:

all:
   hosts:
 hostname: # centos7


this is my literal inventory file: https://paste.debian.net/1215386/
it works for other playbooks, it works for ad-hoc commands (where I
addresse a particular host from that group)


Did you surcharge the python interpreter variable in a config file ? 
(/etc/ansible.cfg, ~/.ansible.cfg, etc...)


See:
https://docs.ansible.com/ansible/latest/reference_appendices/config.html

Regards,

--
Jean-Yves LENHOF

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1a5189ff5c956aa7b82a6352ee28cc1a%40lenhof.eu.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[Stefan Hornburg (Racke)]

On 14/10/2021 14:23, dulhaver via Ansible Project wrote:

the '# centos7' comment on 2 targets is legal I believe.
To rule this out I have removed it for a test run. Still the error was present


Somewhere the value /usr/bin/python3 must come from ... try to grep for this 
string through all relevant directories.

Regards

   Racke


On 10/14/2021 2:14 PM dulha...@mailbox.org wrote:

  

On 10/14/2021 1:44 PM Sandip Bhattacharya  wrote:

  
On 14.10.21 11:49, dulhaver via Ansible Project wrote:

I am running a playbook to install postgresql  
against a centos7 (python 2.75) target and am getting this error about a bad python 
interpreter .

I try to solve this via the inventory.yml

all:
    hosts:
      [hostname]: # centos7

Is this literally what is in your inventory.yaml file? Is that even valid yaml?
Shouldn't it be:

all:
hosts:
  hostname: # centos7


this is my literal inventory file: https://paste.debian.net/1215386/
it works for other playbooks, it works for ad-hoc commands (where I addresse a 
particular host from that group)



--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/198061a5-4f5f-e241-45ef-293283b6ac1a%40linuxia.de.


OpenPGP_0x5B93015BFA2720F8.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

the '# centos7' comment on 2 targets is legal I believe. 
To rule this out I have removed it for a test run. Still the error was present



> On 10/14/2021 2:14 PM dulha...@mailbox.org wrote:
> 
>  
> > On 10/14/2021 1:44 PM Sandip Bhattacharya  
> > wrote:
> > 
> >  
> > On 14.10.21 11:49, dulhaver via Ansible Project wrote:
> > > I am running a playbook to install postgresql 
> > >  against a centos7 (python 2.75) 
> > > target and am getting this error about a bad python interpreter 
> > > .
> > > 
> > > I try to solve this via the inventory.yml
> > > 
> > > all:
> > >    hosts:
> > >      [hostname]: # centos7
> > 
> > Is this literally what is in your inventory.yaml file? Is that even valid 
> > yaml?
> > Shouldn't it be:
> > 
> > all:
> >hosts:
> >  hostname: # centos7
> > 
> this is my literal inventory file: https://paste.debian.net/1215386/
> it works for other playbooks, it works for ad-hoc commands (where I addresse 
> a particular host from that group)

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1090834351.99768.1634214235164%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

> On 10/14/2021 1:44 PM Sandip Bhattacharya  wrote:
> 
>  
> On 14.10.21 11:49, dulhaver via Ansible Project wrote:
> > I am running a playbook to install postgresql 
> >  against a centos7 (python 2.75) target 
> > and am getting this error about a bad python interpreter 
> > .
> > 
> > I try to solve this via the inventory.yml
> > 
> > all:
> >    hosts:
> >      [hostname]: # centos7
> 
> Is this literally what is in your inventory.yaml file? Is that even valid 
> yaml?
> Shouldn't it be:
> 
> all:
>hosts:
>  hostname: # centos7
> 
this is my literal inventory file: https://paste.debian.net/1215386/
it works for other playbooks, it works for ad-hoc commands (where I addresse a 
particular host from that group)

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1329595744.99649.1634213698934%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

> On 10/14/2021 1:41 PM dulhaver via Ansible Project 
>  wrote:
> 
>  
> also I can run ad-hoc commands (like ping) on that target successfully (which 
> should proove to some extend that python can be addressed on target, 
> shouldn't it?)

this i.e. also works

ansible [hostname] -m shell -a 'yum install @postgresql -y' --become

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/693359009.99490.1634213006616%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[Sandip Bhattacharya]

On 14.10.21 11:49, dulhaver via Ansible Project wrote:

I am running a playbook to install postgresql  
against a centos7 (python 2.75) target and am getting this error about a bad python 
interpreter .

I try to solve this via the inventory.yml

all:
   hosts:
     [hostname]: # centos7


Is this literally what is in your inventory.yaml file? Is that even valid yaml?
Shouldn't it be:

all:
  hosts:
hostname: # centos7


--
https://blog.sandipb.net
https://twitter.com/sandipb

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c52cc763-db49-ede0-1663-c0f81318a5a4%40showmethesource.org.

Fwd: Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

also I can run ad-hoc commands (like ping) on that target successfully (which 
should proove to some extend that python can be addressed on target, shouldn't 
it?)



> On 10/14/2021 1:37 PM dulhaver via Ansible Project 
>  wrote:
> 
>  
> > On 10/14/2021 1:15 PM 'Jean-Yves LENHOF' via Ansible Project 
> >  wrote:
> > 
> >  
> > Le 2021-10-14 13:05, dulhaver via Ansible Project a écrit :
> > >> On 10/14/2021 12:59 PM 'Jean-Yves LENHOF' via Ansible Project 
> > >>  wrote:
> > >> 
> > >> 
> > >> Le 2021-10-14 12:56, dulhaver via Ansible Project a écrit :
> > >> > thx for the hint
> > >> >
> > >> >> On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project
> > >> >>  wrote:
> > >> >>
> > >> >> Maybe something wrong with alternatives ?
> > >> >> > alternatives --list | grep -i python
> > >> >
> > >> > turns out empty.
> > >> >
> > >> > have tried to get something working with
> > >> >> alternatives --install /usr/bin/python python /usr/bin/python2.7
> > >> >
> > >> > (where /usr/bin/python is already a symlink to /usr/bin/python2 which
> > >> > is a symlink to /usr/bin/python2.7). It did not change anything
> > >> > though.
> > >> >
> > >> > probably it's my incompetence. I never heard about alternatives before
> > >> > (and don't really get it, as I thought the symlinks /usr/bin/python >
> > >> > /usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide
> > >> > anybody looking for python to the right executable. Neither do I get
> > >> > why all of a sudden a playbook requires this where opther playbooks
> > >> > running against the exact same host haven't.
> > >> 
> > >> 
> > >> Running from the same controller server with the same ansible version 
> > >> ?
> > > 
> > > no, I ran all that on the target. doing that on the Ansible controller
> > > server I get:
> > > 
> > > alternatives --list | grep python
> > > python  manual  /usr/bin/python3
> > > python3 auto/usr/bin/python3.6
> > 
> > That's not what I was asking... But you answer indirectly to one of my 
> > questions.
> > You have only one ansible controller as I understand.
> yes, one single controller
>  
> > You seems to say that there were some playbooks which works OK and some 
> > don't on the same targets.
> > Do you use the same ansible version for the the one which are OK and not 
> > OK ? There were some changes between versions of ansible for the python 
> > default interpreter search
> yes same ansible version, no changes in either ansible version, not python
> 
> > Do you use the same inventory ? If not did you force the ansible python
> > interpreter on one and not the other ?
> same inventory, no forcing
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ansible-project+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ansible-project/1806530675.99139.1634211429674%40office.mailbox.org.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1170018749.99174.1634211660788%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

> On 10/14/2021 1:15 PM 'Jean-Yves LENHOF' via Ansible Project 
>  wrote:
> 
>  
> Le 2021-10-14 13:05, dulhaver via Ansible Project a écrit :
> >> On 10/14/2021 12:59 PM 'Jean-Yves LENHOF' via Ansible Project 
> >>  wrote:
> >> 
> >> 
> >> Le 2021-10-14 12:56, dulhaver via Ansible Project a écrit :
> >> > thx for the hint
> >> >
> >> >> On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project
> >> >>  wrote:
> >> >>
> >> >> Maybe something wrong with alternatives ?
> >> >> > alternatives --list | grep -i python
> >> >
> >> > turns out empty.
> >> >
> >> > have tried to get something working with
> >> >> alternatives --install /usr/bin/python python /usr/bin/python2.7
> >> >
> >> > (where /usr/bin/python is already a symlink to /usr/bin/python2 which
> >> > is a symlink to /usr/bin/python2.7). It did not change anything
> >> > though.
> >> >
> >> > probably it's my incompetence. I never heard about alternatives before
> >> > (and don't really get it, as I thought the symlinks /usr/bin/python >
> >> > /usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide
> >> > anybody looking for python to the right executable. Neither do I get
> >> > why all of a sudden a playbook requires this where opther playbooks
> >> > running against the exact same host haven't.
> >> 
> >> 
> >> Running from the same controller server with the same ansible version 
> >> ?
> > 
> > no, I ran all that on the target. doing that on the Ansible controller
> > server I get:
> > 
> > alternatives --list | grep python
> > python  manual  /usr/bin/python3
> > python3 auto/usr/bin/python3.6
> 
> That's not what I was asking... But you answer indirectly to one of my 
> questions.
> You have only one ansible controller as I understand.
yes, one single controller
 
> You seems to say that there were some playbooks which works OK and some 
> don't on the same targets.
> Do you use the same ansible version for the the one which are OK and not 
> OK ? There were some changes between versions of ansible for the python 
> default interpreter search
yes same ansible version, no changes in either ansible version, not python

> Do you use the same inventory ? If not did you force the ansible python
> interpreter on one and not the other ?
same inventory, no forcing

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1806530675.99139.1634211429674%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

['Jean-Yves LENHOF' via Ansible Project]

Le 2021-10-14 13:05, dulhaver via Ansible Project a écrit :
On 10/14/2021 12:59 PM 'Jean-Yves LENHOF' via Ansible Project 
 wrote:



Le 2021-10-14 12:56, dulhaver via Ansible Project a écrit :
> thx for the hint
>
>> On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project
>>  wrote:
>>
>> Maybe something wrong with alternatives ?
>> > alternatives --list | grep -i python
>
> turns out empty.
>
> have tried to get something working with
>> alternatives --install /usr/bin/python python /usr/bin/python2.7
>
> (where /usr/bin/python is already a symlink to /usr/bin/python2 which
> is a symlink to /usr/bin/python2.7). It did not change anything
> though.
>
> probably it's my incompetence. I never heard about alternatives before
> (and don't really get it, as I thought the symlinks /usr/bin/python >
> /usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide
> anybody looking for python to the right executable. Neither do I get
> why all of a sudden a playbook requires this where opther playbooks
> running against the exact same host haven't.


Running from the same controller server with the same ansible version 
?


no, I ran all that on the target. doing that on the Ansible controller
server I get:

alternatives --list | grep python
python  manual  /usr/bin/python3
python3 auto/usr/bin/python3.6


That's not what I was asking... But you answer indirectly to one of my 
questions.

You have only one ansible controller as I understand.

You seems to say that there were some playbooks which works OK and some 
don't on the same targets.
Do you use the same ansible version for the the one which are OK and not 
OK ? There were some changes between versions of ansible for the python 
default interpreter search
Do you use the same inventory ? If not did you force the ansible python 
interpreter on one and not the other ?




Regards,

--
Jean-Yves LENHOF

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/2a183e1d76dca48acb64c88e5695ecf9%40lenhof.eu.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

> On 10/14/2021 12:59 PM 'Jean-Yves LENHOF' via Ansible Project 
>  wrote:
> 
>  
> Le 2021-10-14 12:56, dulhaver via Ansible Project a écrit :
> > thx for the hint
> > 
> >> On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project 
> >>  wrote:
> >> 
> >> Maybe something wrong with alternatives ?
> >> > alternatives --list | grep -i python
> > 
> > turns out empty.
> > 
> > have tried to get something working with
> >> alternatives --install /usr/bin/python python /usr/bin/python2.7
> > 
> > (where /usr/bin/python is already a symlink to /usr/bin/python2 which
> > is a symlink to /usr/bin/python2.7). It did not change anything
> > though.
> > 
> > probably it's my incompetence. I never heard about alternatives before
> > (and don't really get it, as I thought the symlinks /usr/bin/python >
> > /usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide
> > anybody looking for python to the right executable. Neither do I get
> > why all of a sudden a playbook requires this where opther playbooks
> > running against the exact same host haven't.
> 
> 
> Running from the same controller server with the same ansible version ?

no, I ran all that on the target. doing that on the Ansible controller server I 
get:

alternatives --list | grep python
python  manual  /usr/bin/python3
python3 auto/usr/bin/python3.6

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1693914497.98705.1634209548180%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

['Jean-Yves LENHOF' via Ansible Project]

Le 2021-10-14 12:56, dulhaver via Ansible Project a écrit :

thx for the hint

On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project 
 wrote:


Maybe something wrong with alternatives ?
> alternatives --list | grep -i python


turns out empty.

have tried to get something working with

alternatives --install /usr/bin/python python /usr/bin/python2.7


(where /usr/bin/python is already a symlink to /usr/bin/python2 which
is a symlink to /usr/bin/python2.7). It did not change anything
though.

probably it's my incompetence. I never heard about alternatives before
(and don't really get it, as I thought the symlinks /usr/bin/python >
/usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide
anybody looking for python to the right executable. Neither do I get
why all of a sudden a playbook requires this where opther playbooks
running against the exact same host haven't.



Running from the same controller server with the same ansible version ?

Regards,

--
Jean-Yves LENHOF

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1f0e8552caa6b1ddc9383ecc654a307f%40lenhof.eu.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

thx for the hint

> On 10/14/2021 12:16 PM 'Jean-Yves LENHOF' via Ansible Project 
>  wrote:
> 
> Maybe something wrong with alternatives ?
> > alternatives --list | grep -i python

turns out empty. 

have tried to get something working with 
> alternatives --install /usr/bin/python python /usr/bin/python2.7 

(where /usr/bin/python is already a symlink to /usr/bin/python2 which is a 
symlink to /usr/bin/python2.7). It did not change anything though.

probably it's my incompetence. I never heard about alternatives before (and 
don't really get it, as I thought the symlinks /usr/bin/python > 
/usr/bin/python2 > /usr/bin/python2.7) should be sufficient to guide anybody 
looking for python to the right executable. Neither do I get why all of a 
sudden a playbook requires this where opther playbooks running against the 
exact same host haven't.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1580110447.98592.1634208972831%40office.mailbox.org.

Re: [ansible-project] centos7 target - sudden python interpreter trouble

['Jean-Yves LENHOF' via Ansible Project]

Le 2021-10-14 11:49, dulhaver via Ansible Project a écrit :

I am running a playbook to install postgresql [1] against a centos7
(python 2.75) target and am getting this error about a bad python
interpreter [2].

 I try to solve this via the inventory.yml

 all:
  hosts:
 [hostname]: # centos7
  ansible_host: my.domain.org
  ansible_user: username
  ansible_python_interpreter: /usr/bin/python

 (also tried interpreter_python: /usr/bin/python). the error remains
though

 funny fact ... I ran other playbooks successfully against the same
host before even without having specified any python interpreter.

 any ideas what may be going wrong here?





Hi,

Maybe something wrong with alternatives ?

alternatives --list | grep -i python


Regards,

--
Jean-Yves LENHOF

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/bb6de9cb59fd3403fcedc2bf37eb7bdd%40lenhof.eu.org.

[ansible-project] centos7 target - sudden python interpreter trouble

[dulhaver via Ansible Project]

I am running a playbook to install postgresql https://paste.debian.net/1215359/ 
against a centos7 (python 2.75) target and am getting this error about a bad 
python interpreter https://paste.debian.net/1215357/ .

I try to solve this via the inventory.yml

all:
hosts:
[hostname]: # centos7
ansible_host: my.domain.org
ansible_user: username
ansible_python_interpreter: /usr/bin/python

(also tried interpreter_python: /usr/bin/python). the error remains though

funny fact ... I ran other playbooks successfully against the same host before 
even without having specified any python interpreter.

any ideas what may be going wrong here?

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1298110667.97464.1634204971804%40office.mailbox.org.