[ansible-project] Ansible - Router ACL changes

2020-02-18 Thread Ilayaraja Perumal Samy 
Router ACL Changes -
Ansible playbook Execution – While updating the below Router ACL changes in 
router, The playbook execution status was changed, but the changes are not 
replicated in Router and not getting any error message.
Please find the below changes.
Changes: If the existing rule sequence number is modified for new rule with 
same sequence number.
Manual configuration – while updating the same rule change in manual 
configuration. I’m getting error message % Duplicate sequence number
Please check the issue and do the needful.

-- 
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/a4f318ac-f778-4ee3-ac36-d9282e238479%40googlegroups.com.

[ansible-project] not able to run playbook in ansible 2.9.2

2020-02-18 Thread Eric Chang 
I wrote a simple plabook to test ansible_play_name  

---
> - hosts: localhost
>
>   tasks:
> - name: ref playname
>   debug:
> msg:  ansible_play_name
>


I can run the playbook in ansible 2.8 , but get an error in ansible 2.9.2

ansible 2.8.0

>
> (.28) 2020-02-19 11:40:35 [changch@hqdc034 abc_ansible]$ ansible --version
> ansible 2.8.0
>   config file = /home/changch/abc_ansible/ansible.cfg
>   configured module search path = ['/ansible_modules']
>   ansible python module location = 
> /home/changch/abc_ansible/.28/lib/python3.6/site-packages/ansible
>   executable location = /home/changch/abc_ansible/.28/bin/ansible
>   python version = 3.6.8 (default, Oct  7 2019, 12:59:55) [GCC 8.3.0]
> (.28) 2020-02-19 11:40:43 [changch@hqdc034 abc_ansible]$ ansible-playbook 
> playbook.play_name.yml 
>  [WARNING]: No inventory was parsed, only implicit localhost is available
>
>  [WARNING]: provided hosts list is empty, only localhost is available. 
> Note that the implicit localhost does not match 'all'
>
> [DEPRECATION WARNING]: profile_tasks callback, does not support setting 
> 'options', it will work for now,  but this will be 
> required in the future and should be updated,  see the 2.4 porting guide 
> for details.. This feature will be removed in version 
> 2.9. Deprecation warnings can be disabled by setting 
> deprecation_warnings=False in ansible.cfg.
>  [WARNING]: Skipping plugin 
> (/home/changch/abc_ansible/filter_plugins/password.py) as it seems to be 
> invalid: No module named
> 'passlib'
>
>
> PLAY [localhost] 
> *
>
> TASK [Gathering Facts] 
> ***
> ok: [localhost]
>
> TASK [ref playname] 
> **
> ok: [localhost] => {}
>
> MSG:
>
> ansible_play_name
>
>
> PLAY RECAP 
> ***
> localhost  : ok=2changed=0unreachable=0
> failed=0skipped=0rescued=0ignored=0   
>
> TASK: Gathering Facts --- 
> 1.23s
> TASK: ref playname -- 
> 0.01s
>
> Playbook finished: Wed Feb 19 11:40:51 2020, 2 total tasks.  0:00:01 
> elapsed.
>

ansible 2.9.2

(.ve) 2020-02-19 11:36:46 [changch@hqdc034 abc_ansible]$ ansible --version
> ansible 2.9.2
>   config file = /home/changch/abc_ansible/ansible.cfg
>   configured module search path = ['/ansible_modules']
>   ansible python module location = 
> /home/changch/abc_ansible/.ve/lib/python3.6/site-packages/ansible
>   executable location = /home/changch/abc_ansible/.ve/bin/ansible
>   python version = 3.6.8 (default, Oct  7 2019, 12:59:55) [GCC 8.3.0]
> (.ve) 2020-02-19 11:38:36 [changch@hqdc034 abc_ansible]$ 
>
> (.ve) 2020-02-19 11:30:54 [changch@hqdc034 abc_ansible]$ ansible-playbook 
> playbook.play_name.yml 
> [WARNING]: No inventory was parsed, only implicit localhost is available
>
> [WARNING]: provided hosts list is empty, only localhost is available. Note 
> that the implicit localhost does not match 'all'
>
> ERROR! Unexpected Exception, this is probably a bug: 'CallbackModule' 
> object has no attribute 'set_options'
> to see the full traceback, use -vvv
> (.ve) 2020-02-19 11:31:01 [changch@hqdc034 abc_ansible]$
>


according to this issue in github
https://github.com/RedHatSatellite/satellite-clone/issues/238

this problem should been already  fixed couple years ago ?

is there any suggestions to fix that issue ?

-- 
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/6b214f24-8603-4e83-81e6-5ca5a3d62f12%40googlegroups.com.

Re: [ansible-project] Cannot filter with from_json

2020-02-18 Thread Angel Rengifo Cancino 
Hello:

On Tue, Feb 18, 2020 at 7:39 AM Jerome Meyer  wrote:

> I've created one example.fson file :
> # cat files/example.json
> json_example: |
>   {
>   "example_simple": {
>   "name": "simple",
>   "foo": "value",
>   "item": "this"
>   },
>   }
>
> Your JSON has an incorrect syntax. This is how should look like:

{
"json_example": {
"example_simple": {
"name": "simple",
"foo": "value",
"item": "this"
}
}
}

This way, your playbook just runs fine:

- shell: cat example.json
  register: result

- set_fact:
myvar: "{{ result.stdout | from_json }}"

- debug: var=myvar

which produces this output:

TASK [shell]

changed: [localhost]

TASK [set_fact]
*
ok: [localhost]

TASK [debug]

ok: [localhost] => {
"myvar": {
"json_example": {
"example_simple": {
"foo": "value",
"item": "this",
"name": "simple"
}
}
}
}

You can use this to parse your JSON files:

$ python -m json.tool < example.json

As Dick Visser said, it seems you're mixed some kind of YAML+JSON content
which invalidates it at all

-- 
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/CAA3McK9kJ3wUPSYKAn614vpwQCVjfyfAt1wQ3LZMhqo4ye4THA%40mail.gmail.com.

Re: [ansible-project] Doubt regarding loops and conditionals

2020-02-18 Thread Vladimir Botka 
On Tue, 18 Feb 2020 14:45:34 +
Nuno Jordão  wrote:

> Some times I dont like to use the loop: "{{ nulo|default([]) }}" because it
> doesn't say "skipping" and in complex playbook with lots of hosts I like to
> have that feedback.

You might want to find a plugin which fits your needs
https://docs.ansible.com/ansible/latest/plugins/callback.html#plugin-list

> ... I think that, probably, the behaviour changed, and
> the documentation should be more clear in this regard... The conditional is
> not applied only per item but also to the task...
> 
> [...]
> - name: "test loop"
>   debug:
> msg: "test"
>   loop: "{{nulo}}"
>   when: nulo is defined

You're right. "when" is also applied before the loop starts. Let me point to
2 more cases which describe the complexity. The task below

   - debug:
msg: "test"
  loop: "{{ nulo }}"
  when:
- nulo is defined
- item is search('PATTERN')

is skipped because "when" stops evaluating a conjunction after the first
element fails

   skipping: [localhost]


But when the order of the conditions is changed the task

- debug:
msg: "test"
  loop: "{{ nulo }}"
  when:
- item is search('PATTERN')
- nulo is defined

fails because the evaluation of "item" leads to the evaluation of "nulo"

fatal: [localhost]: FAILED! => {"msg": "'nulo' is undefined"}


As a result, I argue that "{{ nulo|default([]) }}" should be preferred in
term of "keep it simple stupid".
https://en.wikipedia.org/wiki/KISS_principle

It's been also discussed here
https://groups.google.com/forum/#!topic/ansible-project/Y1mGC3vrsng

HTH,

-vlado

-- 
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/20200218202244.5a64dae9%40gmail.com.


pgptLLvuXP3Pf.pgp
Description: OpenPGP digital signature

Re: [ansible-project] Ansible expect module with Oracle SBC

2020-02-18 Thread Kai Stian Olstad 
On Tue, Feb 18, 2020 at 02:38:40AM -0800, Gerhard Van Der Wath wrote:
> HI Kai.
> 
> When running this command via Ansible I am getting the following:
> 
> fatal: [##]: FAILED! => {
> "changed": false, 
> "invocation": {
> "module_args": {
> "chdir": null, 
> "command": "ssh admin@#", 
> "creates": null, 
> "echo": false, 
> "removes": null, 
> "responses": {
> "#": [
> "show xcode load -detail", 
> "exit"
> ], 
> "(?i)password": "###"
> }, 
> "timeout": 30
> }
> }, 
> "msg": "No remaining responses for '#', output was 'Sess  Current  

As the message says, expect still get the # prompt but doesn't have any more
responses to type in.


> Maximum\r\n  ===  ===  =  ===  ===\r\n   00   0 14
>  3.33%   29.28%\r\n   00   1 17 2.97%   29.02%\r\n   01   0 -  
>  --\r\n   01   1 -   --\r\n   02   0 -  
>  --\r\n   02   1 -   --\r\n   03   0 -   -  
>   -\r\n   03   1 -   --\r\n   04   0 -   -  
>   -\r\n   04   1 -   --\r\n   05   0 -   -
> -\r\n   05   1 -   --\r\n   06   0 -   -
> -\r\n   06   1 -   --\r\n   07   0 -   -
> -\r\n   07   1 -   --\r\n   08   0 -   -
> -\r\n   08   1 -   --\r\n   09   0 -   -
> -\r\n   09   1 -   --\r\n   10   0 -   -
> -\r\n   10   1 -   --\r\n   11   0 -   -
> -\r\n   11   1 -   --\r\nSBCHA1#'"

The last part "\r\nSBCHA1#" show that expect get the prompt again.

> The output of the command is as below:
> 
> HA1# show xcode load -detail
> 12:37:54
> Total Sessions:334
>   - Load -
>   TCM  DSP  #Sess  Current  Maximum

In the output you have a #. Since you have said to expect that "#" is the sting
to trigger a response it will type exit here, but since this is not the
prompt this causes issues.

The text expect should trigger on in responses has to be unique, an in you case
# is not. So you need to add more characters to it.
If the prompt always is "BCHA1#" you can use that instead of only "#"


-- 
Kai Stian Olstad

-- 
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/20200218160601.geskqbuvmww7l7ly%40olstad.com.

Re: [ansible-project] deployment failing in ansible

2020-02-18 Thread Dick Visser 
Don’t expect people to do all the work of downloading and unpacking random
mystery/binary files.
Instead you are expected to provide the playbook/task etc in the easiest
way possible for us to understand the problem.

So, please tell clearly:


- What you are trying to achieve.

- How you are doing this.

- What problems you encounter.

- Which command did you run, and what output did you get from that (copied
as text, not as images/attachments/screenshots)

- What the relevant tasks/playbooks/code/variables look like




On Tue, 18 Feb 2020 at 16:17, Nishu Sinha  wrote:

> I have attached the application zip file with tasks and  templates
>
> On Tue, Feb 18, 2020 at 10:15 AM Stefan Hornburg (Racke) 
> wrote:
>
>> On 2/18/20 4:06 PM, Nishu Sinha wrote:
>> > Hi
>> >
>> > I am getting the below error when i am trying to deploy the
>> application NCS  via Jenkins using ansible scripts
>> >
>>
>> This is really off topic here due to missing information (playbook, task,
>> ...).
>>
>> Regards
>>   Racke
>>
>> >
>> >
>> > TASK [ncs-ansible : Run install.sh]
>> 
>> > task path: /automation/roles/ncs-ansible/tasks/7-app.yml:67
>> > fatal: [ncs]: FAILED! => {"changed": true, "cmd": "echo 'yes' |
>> /opt/cts/nbms/install.sh Tomee", "delta":
>> > "0:00:00.376643", "end": "2020-02-18 13:28:51.645130", "msg": "non-zero
>> return code", "rc": 1, "start": "2020-02-18
>> > 13:28:51.268487", "stderr": "Error: Unable to access jarfile
>> @INSTALL_JAR@\nError: Unable to access jarfile
>> > @INSTALL_JAR@", "stderr_lines": ["Error: Unable to access jarfile
>> @INSTALL_JAR@", "Error: Unable to access jarfile
>> > @INSTALL_JAR@"], "stdout": "\n - Settings -\n
>> JAVA_HOME=/opt/cts/jdk1.8.0_131\n
>> > \n\n  tokenCopy
>>  installer/installer.sh to /opt/cts/nbms/installer.sh",
>> > "stdout_lines": ["", " - Settings -", "
>> JAVA_HOME=/opt/cts/jdk1.8.0_131", "
>> > ", "", "  tokenCopy
>>  installer/installer.sh to /opt/cts/nbms/installer.sh"]}
>> >
>> > PLAY RECAP
>> *
>> > ncs: ok=55   changed=14   unreachable=0
>>  failed=1skipped=9rescued=0ignored=0
>> >
>> > --
>> > 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 > ansible-project+unsubscr...@googlegroups.com>.
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/ansible-project/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com
>> > <
>> https://groups.google.com/d/msgid/ansible-project/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>>
>>
>> --
>> Ecommerce and Linux consulting + Perl and web application programming.
>> Debian and Sympa administration. Provisioning with Ansible.
>>
>> --
>> 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/3c9fa8d2-01bc-a592-7f8b-e6248908c4b4%40linuxia.de
>> .
>>
> --
> 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/CADG8R8xB1J8fWCyNH%2B4pLRmgtFYRtd0x2TS05jLa9KTHO_HbcQ%40mail.gmail.com
> 
> .
>
-- 
Sent from a mobile device - please excuse the brevity, spelling and
punctuation.

-- 
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/CAL8fbwObpsx9ZRDNhu%2BcN9C63%3D%3Do0s1J1t%2B%2BQNVQ6xVEgs2DcA%40mail.gmail.com.

Re: [ansible-project] Cannot filter with from_json

2020-02-18 Thread Dick Visser 
On Tue, 18 Feb 2020 at 13:39, Jerome Meyer  wrote:

> Hi Team,
>
> I'm encountered some issue with set_facts from variable with json and for
> this reason I'm tried to understand this. To reproduce this case I'm using
> the example from here : playbooks filters
> 
>
> tasks
>   - shell: cat /some/path/to/file.json
> register: result
>
>   - set_fact:
>   myvar: "{{ result.stdout | from_json }}"
>
>
This here below looks like your example.json file actually contains yaml
which in turn contains json?


> I've created one example.fson file :
> # cat files/example.json
> json_example: |
>   {
>   "example_simple": {
>   "name": "simple",
>   "foo": "value",
>   "item": "this"
>   },
>   }
>
>
> Here's the task file :
> # cat tasks/main.yml
> ---
> - name: Read JSON file
>   shell: cat ../files/example.json
>   register: json
>
> - name: Get simple value.
>   set_fact:
> simple_value: "{{ (json.stdout | from_json).example_simple.name }}"
>
>
> - name: Simple debug.
>   debug:
> msg: "{{ simple_value }}"
>
>
> And here the result:
> fatal: [localhost]: FAILED! => {"msg": "the field 'args' has an invalid
> value ({u'simple_value': u'{{ (json.stdout | from_json) }}'}), and could
> not be converted to an dict.The error was: No JSON object could be
> decoded\n\nThe error appears to be in
> '/etc/ansible/roles/testrole/tasks/main.yml': line 7, column 3, but may\nbe
> elsewhere in the file depending on the exact syntax problem.\n\nThe
> offending line appears to be:\n\n\n- name: Get simple value.\n  ^ here\n"}
>
> It tells me that the input cannot be converted to dict, But why and what
> is the problem? Could someone explain me this problem?
> I cannot understand what is wrong.
>
> Best regards, J
>
>
>
>
>
>
> --
> 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/76189198-429c-4025-98f8-92e7f69ff417%40googlegroups.com
> 
> .
>
-- 
Sent from a mobile device - please excuse the brevity, spelling and
punctuation.

-- 
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/CAL8fbwMgyNjhT0Kmgy80DBj4ykeUEMMar6_7rUc4i8nDrcLvuQ%40mail.gmail.com.

Re: [ansible-project] Cannot filter with from_json

2020-02-18 Thread Kai Stian Olstad 
On Tue, Feb 18, 2020 at 04:39:27AM -0800, Jerome Meyer wrote:
> Hi Team,
> 
> I'm encountered some issue with set_facts from variable with json and for 
> this reason I'm tried to understand this. To reproduce this case I'm using 
> the example from here : playbooks filters 
> 
> 
> tasks
>   - shell: cat /some/path/to/file.json 
> register: result 
> 
>   - set_fact: 
>   myvar: "{{ result.stdout | from_json }}"
> 
> 
> I've created one example.fson file :
> # cat files/example.json
> json_example: |
>   {
>   "example_simple": {
>   "name": "simple",
>   "foo": "value",
>   "item": "this"
>   },
>   }

This is not correct json syntax.
It looks like yaml json_example multiline with an incorrectly syntax json in
it.


-- 
Kai Stian Olstad

-- 
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/20200218154904.ncpnvwf7y4lukkot%40olstad.com.

Re: [ansible-project] deployment failing in ansible

2020-02-18 Thread Nishu Sinha 
I have attached the application zip file with tasks and  templates

On Tue, Feb 18, 2020 at 10:15 AM Stefan Hornburg (Racke) 
wrote:

> On 2/18/20 4:06 PM, Nishu Sinha wrote:
> > Hi
> >
> > I am getting the below error when i am trying to deploy the  application
> NCS  via Jenkins using ansible scripts
> >
>
> This is really off topic here due to missing information (playbook, task,
> ...).
>
> Regards
>   Racke
>
> >
> >
> > TASK [ncs-ansible : Run install.sh]
> 
> > task path: /automation/roles/ncs-ansible/tasks/7-app.yml:67
> > fatal: [ncs]: FAILED! => {"changed": true, "cmd": "echo 'yes' |
> /opt/cts/nbms/install.sh Tomee", "delta":
> > "0:00:00.376643", "end": "2020-02-18 13:28:51.645130", "msg": "non-zero
> return code", "rc": 1, "start": "2020-02-18
> > 13:28:51.268487", "stderr": "Error: Unable to access jarfile
> @INSTALL_JAR@\nError: Unable to access jarfile
> > @INSTALL_JAR@", "stderr_lines": ["Error: Unable to access jarfile
> @INSTALL_JAR@", "Error: Unable to access jarfile
> > @INSTALL_JAR@"], "stdout": "\n - Settings -\n
> JAVA_HOME=/opt/cts/jdk1.8.0_131\n
> > \n\n  tokenCopy
>  installer/installer.sh to /opt/cts/nbms/installer.sh",
> > "stdout_lines": ["", " - Settings -", "
> JAVA_HOME=/opt/cts/jdk1.8.0_131", "
> > ", "", "  tokenCopy
>  installer/installer.sh to /opt/cts/nbms/installer.sh"]}
> >
> > PLAY RECAP
> *
> > ncs: ok=55   changed=14   unreachable=0
>  failed=1skipped=9rescued=0ignored=0
> >
> > --
> > 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  ansible-project+unsubscr...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/ansible-project/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/ansible-project/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>
> --
> Ecommerce and Linux consulting + Perl and web application programming.
> Debian and Sympa administration. Provisioning with Ansible.
>
> --
> 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/3c9fa8d2-01bc-a592-7f8b-e6248908c4b4%40linuxia.de
> .
>

-- 
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/CADG8R8xB1J8fWCyNH%2B4pLRmgtFYRtd0x2TS05jLa9KTHO_HbcQ%40mail.gmail.com.


nifi-ansible.7z
Description: Binary data

Re: [ansible-project] deployment failing in ansible

2020-02-18 Thread Stefan Hornburg (Racke) 
On 2/18/20 4:06 PM, Nishu Sinha wrote:
> Hi 
> 
> I am getting the below error when i am trying to deploy the  application NCS  
> via Jenkins using ansible scripts
> 

This is really off topic here due to missing information (playbook, task, ...).

Regards
  Racke

> 
> 
> TASK [ncs-ansible : Run install.sh] 
> 
> task path: /automation/roles/ncs-ansible/tasks/7-app.yml:67
> fatal: [ncs]: FAILED! => {"changed": true, "cmd": "echo 'yes' | 
> /opt/cts/nbms/install.sh Tomee", "delta":
> "0:00:00.376643", "end": "2020-02-18 13:28:51.645130", "msg": "non-zero 
> return code", "rc": 1, "start": "2020-02-18
> 13:28:51.268487", "stderr": "Error: Unable to access jarfile 
> @INSTALL_JAR@\nError: Unable to access jarfile
> @INSTALL_JAR@", "stderr_lines": ["Error: Unable to access jarfile 
> @INSTALL_JAR@", "Error: Unable to access jarfile
> @INSTALL_JAR@"], "stdout": "\n - Settings -\n 
> JAVA_HOME=/opt/cts/jdk1.8.0_131\n
> \n\n  tokenCopy  installer/installer.sh 
> to /opt/cts/nbms/installer.sh",
> "stdout_lines": ["", " - Settings -", " 
> JAVA_HOME=/opt/cts/jdk1.8.0_131", "
> ", "", "  tokenCopy  
> installer/installer.sh to /opt/cts/nbms/installer.sh"]}
> 
> PLAY RECAP 
> *
> ncs                        : ok=55   changed=14   unreachable=0    failed=1   
>  skipped=9    rescued=0    ignored=0   
> 
> -- 
> 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/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com
> .


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

-- 
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/3c9fa8d2-01bc-a592-7f8b-e6248908c4b4%40linuxia.de.


signature.asc
Description: OpenPGP digital signature

[ansible-project] deployment failing in ansible

2020-02-18 Thread Nishu Sinha 
Hi

I am getting the below error when i am trying to deploy the  application
NCS  via Jenkins using ansible scripts

TASK [ncs-ansible : Run install.sh]

task path: /automation/roles/ncs-ansible/tasks/7-app.yml:67
fatal: [ncs]: FAILED! => {"changed": true, "cmd": "echo 'yes' |
/opt/cts/nbms/install.sh Tomee", "delta": "0:00:00.376643", "end":
"2020-02-18 13:28:51.645130", "msg": "non-zero return code", "rc": 1,
"start": "2020-02-18 13:28:51.268487", "stderr": "Error: Unable to access
jarfile @INSTALL_JAR@\nError: Unable to access jarfile @INSTALL_JAR@",
"stderr_lines": ["Error: Unable to access jarfile @INSTALL_JAR@", "Error:
Unable to access jarfile @INSTALL_JAR@"], "stdout": "\n -
Settings -\n JAVA_HOME=/opt/cts/jdk1.8.0_131\n
\n\n  tokenCopy  installer/installer.sh
to /opt/cts/nbms/installer.sh", "stdout_lines": ["", " -
Settings -", " JAVA_HOME=/opt/cts/jdk1.8.0_131", "
", "", "  tokenCopy
 installer/installer.sh to /opt/cts/nbms/installer.sh"]}

PLAY RECAP
*
ncs: ok=55   changed=14   unreachable=0failed=1
   skipped=9rescued=0ignored=0

-- 
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/CADG8R8wCt-sUK-Z1vjehZdDtN3_F4KF9i6WZSXiEQsAHE_KF9g%40mail.gmail.com.

Re: [ansible-project] Doubt regarding loops and conditionals

2020-02-18 Thread Stefan Hornburg (Racke) 
On 2/18/20 3:45 PM, Nuno Jordão wrote:
> Hello,
> 
> Thank you for your responses.
> Some times I dont like to use the loop: "{{ nulo|default([]) }}" because it 
> doesn't say "skipping" and in complex
> playbook with lots of hosts I like to have that feedback. 
> 
> I tested several options and and everything works, even the case of the issue 
> 45976
>  (should have tested that 
> one before). I think that, probably, the
> behaviour changed, and the documentation should be more clear in this 
> regard... The conditional is not applied only per
> item but also to the task...
> 

I suppose Ansible determines whether the conditional contains a loop variable. 
In that case it applies it for every
item. In the other case it evaluates it only once and skips the task when the 
conditional results in a false value.

The documentation seems not be completely accurate.

Regards
 Racke

>   vars:
>     tstbool: False
>     tstnull:
> 
>   tasks:
> 
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo|default([])}}"
> 
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo}}"
>       when: nulo is defined
> 
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo}}"
>       when: nulo|default(False)
> 
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo}}"
>       when: nulo|default([])|length > 0
> 
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo}}"
>       when: tstbool
>   
>     - name: "test loop"
>       debug:
>         msg: "test"
>       loop: "{{nulo}}"
>       when: tstnull
> 
> Returns:
> 
> PLAY [localhost] 
> *
> 
> TASK [test loop] 
> *
> 
> TASK [test loop] 
> *
> skipping: [localhost]
> 
> TASK [test loop] 
> *
> skipping: [localhost]
> 
> TASK [test loop] 
> *
> skipping: [localhost]
> 
> TASK [test loop] 
> *
> skipping: [localhost]
> 
> TASK [test loop]
> *[DEPRECATION
> WARNING]: evaluating None as a bare variable, this behaviour will go away and 
> you might need to add
> |bool to the expression in the future. Also see CONDITIONAL_BARE_VARS 
> configuration toggle.. This feature will be
> removed in version 2.12. Deprecation warnings can be disabled by setting 
> deprecation_warnings=False in ansible.cfg.
> skipping: [localhost]
> 
> PLAY RECAP
> ***localhost
>     
>              : ok=0    changed=0    unreachable=0    failed=0    skipped=6    
> rescued=0    ignored=0
> 
> The final count for skipped is 6 but the first task doesn't report skipping
> 
> 
> On Mon, Feb 17, 2020 at 9:10 PM Vladimir Botka  > wrote:
> 
> On Mon, 17 Feb 2020 20:11:07 +
> Nuno Jordão mailto:nuno.jor...@gmail.com>> wrote:
> 
> >     - name: "test loop"
> >       debug:
> >         msg: "test"
> >       loop: "{{nulo}}"
> >       when: nulo is defined
> >
> > where "nulo" is an undefined variable. Here the task skips instead of
> > failing.
> 
> Instead of testing whether the variable is defined or not, use the 
> "default"
> filter. For example
> 
>      - name: "test loop"
>        debug:
>          msg: "test"
>        loop: "{{ nulo|default([]) }}"
> 
> The loop will be skipped if "nulo" is undefined. Test "nulo" separately if
> you want the playbook to fail. For example
> 
>      - name: Fail when nulo undefined
>        fail:
>          msg: "Variable nulo undefined"
>        when: nulo if undefined
> 
> HTH,
> 
>         -vlado
> 
> -- 
> 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/CAEAA%3Dtv3rn4Wh_txsEr7P92ec5g7DSwWp6uhWRZDeHoyZQ-z2w%40mail.gmail.com
>

Re: [ansible-project] Ansible when logic to determine whether to use yum or dnf to install packages on ansible_os_family='RedHat'

2020-02-18 Thread Donald Jones 
Thanks. That looks like a good option:
https://ansible-tips-and-tricks.readthedocs.io/en/latest/os-dependent-tasks/installing_packages/

I think that it comes down to:
- continue using apt for Debian systems (due to field changes)
- use {ansible_pkg_mgr} for RedHat / Fedora systems (as their parameters 
are mostly aligned)

-- 
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/9d10a6af-caf8-42c4-9ae9-d5d516af883e%40googlegroups.com.

Re: [ansible-project] Doubt regarding loops and conditionals

2020-02-18 Thread Nuno Jordão 
Hello,

Thank you for your responses.
Some times I dont like to use the loop: "{{ nulo|default([]) }}" because it
doesn't say "skipping" and in complex playbook with lots of hosts I like to
have that feedback.

I tested several options and and everything works, even the case of the
issue 45976  (should have
tested that one before). I think that, probably, the behaviour changed, and
the documentation should be more clear in this regard... The conditional is
not applied only per item but also to the task...

  vars:
tstbool: False
tstnull:

  tasks:

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo|default([])}}"

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo}}"
  when: nulo is defined

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo}}"
  when: nulo|default(False)

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo}}"
  when: nulo|default([])|length > 0

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo}}"
  when: tstbool

- name: "test loop"
  debug:
msg: "test"
  loop: "{{nulo}}"
  when: tstnull

Returns:

PLAY [localhost]
*

TASK [test loop]
*

TASK [test loop]
*
skipping: [localhost]

TASK [test loop]
*
skipping: [localhost]

TASK [test loop]
*
skipping: [localhost]

TASK [test loop]
*
skipping: [localhost]

TASK [test loop]
*[DEPRECATION
WARNING]: evaluating None as a bare variable, this behaviour will go away
and you might need to add
|bool to the expression in the future. Also see CONDITIONAL_BARE_VARS
configuration toggle.. This feature will be
removed in version 2.12. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
skipping: [localhost]

PLAY RECAP
***localhost
 : ok=0changed=0unreachable=0failed=0
 skipped=6rescued=0ignored=0

The final count for skipped is 6 but the first task doesn't report skipping


On Mon, Feb 17, 2020 at 9:10 PM Vladimir Botka  wrote:

> On Mon, 17 Feb 2020 20:11:07 +
> Nuno Jordão  wrote:
>
> > - name: "test loop"
> >   debug:
> > msg: "test"
> >   loop: "{{nulo}}"
> >   when: nulo is defined
> >
> > where "nulo" is an undefined variable. Here the task skips instead of
> > failing.
>
> Instead of testing whether the variable is defined or not, use the
> "default"
> filter. For example
>
>  - name: "test loop"
>debug:
>  msg: "test"
>loop: "{{ nulo|default([]) }}"
>
> The loop will be skipped if "nulo" is undefined. Test "nulo" separately if
> you want the playbook to fail. For example
>
>  - name: Fail when nulo undefined
>fail:
>  msg: "Variable nulo undefined"
>when: nulo if undefined
>
> HTH,
>
> -vlado
>

-- 
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/CAEAA%3Dtv3rn4Wh_txsEr7P92ec5g7DSwWp6uhWRZDeHoyZQ-z2w%40mail.gmail.com.

[ansible-project] Cannot filter with from_json

2020-02-18 Thread Jerome Meyer 
Hi Team,

I'm encountered some issue with set_facts from variable with json and for 
this reason I'm tried to understand this. To reproduce this case I'm using 
the example from here : playbooks filters 


tasks
  - shell: cat /some/path/to/file.json 
register: result 

  - set_fact: 
  myvar: "{{ result.stdout | from_json }}"


I've created one example.fson file :
# cat files/example.json
json_example: |
  {
  "example_simple": {
  "name": "simple",
  "foo": "value",
  "item": "this"
  },
  }


Here's the task file :
# cat tasks/main.yml
---
- name: Read JSON file 
  shell: cat ../files/example.json
  register: json
  
- name: Get simple value.
  set_fact:
simple_value: "{{ (json.stdout | from_json).example_simple.name }}"


- name: Simple debug.
  debug:
msg: "{{ simple_value }}"


And here the result:
fatal: [localhost]: FAILED! => {"msg": "the field 'args' has an invalid 
value ({u'simple_value': u'{{ (json.stdout | from_json) }}'}), and could 
not be converted to an dict.The error was: No JSON object could be 
decoded\n\nThe error appears to be in 
'/etc/ansible/roles/testrole/tasks/main.yml': line 7, column 3, but may\nbe 
elsewhere in the file depending on the exact syntax problem.\n\nThe 
offending line appears to be:\n\n\n- name: Get simple value.\n  ^ here\n"}

It tells me that the input cannot be converted to dict, But why and what is 
the problem? Could someone explain me this problem?
I cannot understand what is wrong.

Best regards, J






-- 
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/76189198-429c-4025-98f8-92e7f69ff417%40googlegroups.com.

[ansible-project] Re: List of hosts by MacAdress + Connexion if computer is in standby

2020-02-18 Thread Test Deux 
Ok, thanx guys :)

-- 
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/e8f2040a-6dcb-4235-9cd1-30592a2c1f91%40googlegroups.com.

[ansible-project] Re: Ansible-vault password file not found

2020-02-18 Thread haohao qiang 
Hello, i have the same issue, did you resolved? How to make it work!

在 2018年3月8日星期四 UTC+8下午9:03:18，JiElPe-Fr38写道：
>
> Thanks for the idea... 
> In fact, I already used the verbose mode, so yes I can confirm that it 
> uses the awaited config file.
> Which is not a good news, because it would have been a good reason for the 
> problem.
>
> J-L
>
> Le jeudi 8 mars 2018 11:49:16 UTC+1, JiElPe-Fr38 a écrit :
>>
>> Dear all,
>>
>> I am "auto learning" ansible and currently try to understand how to use 
>> vault.
>> To summarize things, I have created a vault.yml file in the vars 
>> directory, and included it in the main.yml task. Then, I put the vault 
>> password within a .vault_passwd file created at the same level than 
>> ansible.cfg.
>>
>> When I run :
>> ansible-playbook with --vault-password-file .vault_passwd
>>
>> It is ok.
>>
>> So, I tried to put the vault password file path within ansible.cfg as 
>> follows :
>> vault_password_file = .vault_passwd
>>
>> When running the playbook (without --vault-password-file ), it fails with 
>> :
>> fatal: [ci-server]: FAILED! => {
>> "ansible_facts": {},
>> "ansible_included_var_files": [],
>> "changed": false,
>> "message": "Attempting to decrypt but no vault secrets found"
>> }
>>
>> at the line were the vault.yml file is imported. So, it looks like if it 
>> does not find the vault password file to decrypt the vault file.
>>
>> I can't understand why, and have already tried with the aboslute path, or 
>> changing _ with -, just in case documentation had a typo... but without any 
>> success.
>>
>> If someone could have an idea to help, I would be glad.
>>
>> Have a nice day!
>>
>> J-L
>>
>

-- 
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/94a3bebb-0b2c-49e8-bac2-006963c56d6f%40googlegroups.com.

Re: [ansible-project] Ansible expect module with Oracle SBC

2020-02-18 Thread Gerhard Van Der Wath 
HI Kai.

When running this command via Ansible I am getting the following:

The full traceback is:
  File 
"/tmp/ansible_expect_payload__etk4d92/ansible_expect_payload.zip/ansible/modules/commands/expect.py",
 
line 123, in wrapped

fatal: [##]: FAILED! => {
"changed": false, 
"invocation": {
"module_args": {
"chdir": null, 
"command": "ssh admin@#", 
"creates": null, 
"echo": false, 
"removes": null, 
"responses": {
"#": [
"show xcode load -detail", 
"exit"
], 
"(?i)password": "###"
}, 
"timeout": 30
}
}, 
"msg": "No remaining responses for '#', output was 'Sess  Current  
Maximum\r\n  ===  ===  =  ===  ===\r\n   00   0 14
 3.33%   29.28%\r\n   00   1 17 2.97%   29.02%\r\n   01   0 -  
 --\r\n   01   1 -   --\r\n   02   0 -  
 --\r\n   02   1 -   --\r\n   03   0 -   -  
  -\r\n   03   1 -   --\r\n   04   0 -   -  
  -\r\n   04   1 -   --\r\n   05   0 -   -
-\r\n   05   1 -   --\r\n   06   0 -   -
-\r\n   06   1 -   --\r\n   07   0 -   -
-\r\n   07   1 -   --\r\n   08   0 -   -
-\r\n   08   1 -   --\r\n   09   0 -   -
-\r\n   09   1 -   --\r\n   10   0 -   -
-\r\n   10   1 -   --\r\n   11   0 -   -
-\r\n   11   1 -   --\r\nSBCHA1#'"
}


The output of the command is as below:

HA1# show xcode load -detail
12:37:54
Total Sessions:334
  - Load -
  TCM  DSP  #Sess  Current  Maximum
  ===  ===  =  ===  ===
   00   0 8518.78%   32.74%
   00   1 8218.80%   32.80%
   01   0 8218.58%   32.70%
   01   1 8518.56%   32.68%
   02   0 -   --
   02   1 -   --
   03   0 -   --
   03   1 -   --
   04   0 -   --
   04   1 -   --
   05   0 -   --
   05   1 -   --
   06   0 -   --
   06   1 -   --
   07   0 -   --
   07   1 -   --
   08   0 -   --
   08   1 -   --
   09   0 -   --
   09   1 -   --
   10   0 -   --
   10   1 -   --
   11   0 -   --
   11   1 -   --

I am guessing it is the - character that may be causing an issue?

On Thursday, 13 February 2020 12:14:49 UTC+2, Kai Stian Olstad wrote:
>
> On Thu, Feb 13, 2020 at 01:22:37AM -0800, Gerhard Van Der Wath wrote: 
> > Thank you Kai. 
> > 
> > I think I am making progress, is this the output that is expected: 
> > 
> > "*   
>   
> > *", 
> > "*   Disconnect IMMEDIATELY if you are not an authorized user!   
>   
> > *", 
> > "*All access and use may be monitored and/or recorded.   
>  * 
> > ", 
> > "*   
>   
> > *", 
> > 
> > "**", 
> > "", 
> > "", 
> > "SBCHA1# show sessions", 
> > "11:17:24-107 Capacity=4000", 
> > "Session Statistics-- Period --  Lifetime 
> > ", 
> > "ActiveHigh   Total  Total  PerMax   
>   
> > High", 
> > "Total Sessions160616613346  128530803   15238   
>   
> > 2452", 
> > "SIP Sessions  160616613346  128530803   15238   
>   
> > 2452", 
> > "H.323 Calls  0   0   0  0   0   
> 
> >  0", 
> > "", 
> > "SIP Audio/Video Statistics-- Period --  Lifetime 
> > ", 
> > "ActiveHigh   Total  Total  PerMax   
>   
> > High", 
> > "Audio Calls   154115922582   906991178060   
>   
> > 2096", 
> > "Video Calls  0   0   0113   7   
> 
> >  2", 
> > "Messaging Sessions   0   0   0  0   0   
> 
> >  0", 
> > "SBCHA1# sh platform cpu-load", 
> > "Timestamp: 11:17:24 Thu 2020-02-13", 
> > "Total load   : 9%", 
> > "CPU 00 load  : 9%", 
> > "CPU 01 load  : 9%", 
> > "CPU 02 load  : 10%", 
> > "CPU 03 load  : 9%", 
> > "SBCHA1# exit", 
> > "SBCHA1> " 
> > ] 
>
> It is as expected. 
>

Re: [ansible-project] Ansible when logic to determine whether to use yum or dnf to install packages on ansible_os_family='RedHat'

2020-02-18 Thread Martin Krizek 
On Tue, Feb 18, 2020 at 11:30 AM Vladimir Botka  wrote:
>
> On Tue, 18 Feb 2020 01:25:18 -0800 (PST)
> Donald Jones  wrote:
>
> > Up until now I've been making a logic decision with my ansible roles based
> > upon the ansible_os_family, to run the appropriate module for yum
> > ('RedHat') or apt ('Debian').

You can use `ansible_pkg_mgr` variable instead.

M.

> >
> > With the introduction of CentOS 8, dnf has been brought in as a replacement
> > for yum.
> > So my question is, is there a prefered 'when' logic that I can use to
> > determine whether I should use the dnf or yum module in a playbook/role?
> > Ideally something that maximises future proof.

-- 
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/CADDq2EPGTPM2tLk-hr1vfRopJP-V_7i6Ngte6WNo925tokioKg%40mail.gmail.com.

Re: [ansible-project] Ansible when logic to determine whether to use yum or dnf to install packages on ansible_os_family='RedHat'

2020-02-18 Thread Vladimir Botka 
On Tue, 18 Feb 2020 01:25:18 -0800 (PST)
Donald Jones  wrote:

> Up until now I've been making a logic decision with my ansible roles based 
> upon the ansible_os_family, to run the appropriate module for yum 
> ('RedHat') or apt ('Debian').
> 
> With the introduction of CentOS 8, dnf has been brought in as a replacement 
> for yum. 
> So my question is, is there a prefered 'when' logic that I can use to 
> determine whether I should use the dnf or yum module in a playbook/role? 
> Ideally something that maximises future proof.

It's possible to use "package – Generic OS package manager". The selection of
the package manager is automatic by default.
https://docs.ansible.com/ansible/latest/modules/package_module.html

HTH,

-vlado

-- 
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/20200218112959.1b44c6e6%40gmail.com.


pgp6t53hXuSjV.pgp
Description: OpenPGP digital signature

[ansible-project] Ansible when logic to determine whether to use yum or dnf to install packages on ansible_os_family='RedHat'

2020-02-18 Thread Donald Jones 
Hi,

Up until now I've been making a logic decision with my ansible roles based 
upon the ansible_os_family, to run the appropriate module for yum 
('RedHat') or apt ('Debian').

With the introduction of CentOS 8, dnf has been brought in as a replacement 
for yum. 
So my question is, is there a prefered 'when' logic that I can use to 
determine whether I should use the dnf or yum module in a playbook/role? 
Ideally something that maximises future proof.

Regards

Donald



-- 
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/9b5542e9-95fd-4bb5-8e89-14931c9c58c1%40googlegroups.com.