I've been using become:yes and become_user:logstash in a playbook to install
extra plugins. It all works great with ansible 2.3.1.0. I mistakenly ran the
playbook using the devel branch (2.4) and the shell module suddently broke.
I still consider it a bug as it's a backward incompatible change a
Even with passwordless sudo, you may still want to use become:yes to
actually invoke the command using sudo.
Le jeudi 13 juillet 2017 19:59:59 UTC+2, swapnil bendekar a écrit :
>
> Hello Folks,
>
> With Ansible(2.3.0.0) and python(2.6.6), executing ansible playbook from
> webadmin user.
> Usi
Can you share a link to the issue that was closed or at least share the
playbook so we can have a chance understanding what is going on.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails
This error is harmless. Hosts are openstack VMs configured from a single
instance snapshot (so they are identical each time). The error is due to
/etc/hosts not containing a reference to the content of /etc/hostname. I can
provide an execution stack with this error removed on monday if need be.
Sure, but on monday only :/. I don't have access to those machines from home.
--
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...@goog
Here is the task executing with ansible 2.3.1.0 and a broken /etc/hosts. I
also updated the issue on github to provide these informations after fixing
/etc/hosts (and thus removing the warning from sudo).
TASK [Install logstash-output-influxdb]
task path
Code block seems to have messed things up. Here is the result verbatim:
TASK [Install logstash-output-influxdb]
task path: /home/kniyl/debug.yml:21
Using module file
/usr/lib/python2.7/site-packages/ansible/modules/commands/command.py
<172.20.34.42> ESTAB
Almost. It's the first value in a whitespace separated line, which means
'foo bar' and 'foo\n \tbar' would both be splitted to ['foo', 'bar'] and
element 0 is 'foo' for both.
On a side note, split() without arguments has extra logic that make the
call to strip() redundant.
Lastly, nfs_exports
It seems like `with_items` is indented inside `blockinfile`, it should be
at the same level:
- blockinfile:
path: /etc/apache2/sites-enabled/"{{ item }}".php.qarea.org.conf
block: |
AssignUserId "{{ item }}" "{{ item }}"
insertbefore:
Did you
try
http://docs.ansible.com/ansible/latest/playbooks_filters.html#combining-hashes-dictionaries
?
Le mardi 18 juillet 2017 15:11:17 UTC+2, Riccardo Murri a écrit :
>
> Hello,
>
> I would like to write a playbook that does the following:
>
> 1. Read a list of source URLs + other met
I'm still interested into knowing how to make this task work with ansible
2.4.
Since the github issue is still closed, this doesn't seem to be considered
a bug, so I need advices about fixing my playbook.
Thanks.
Le lundi 17 juillet 2017 10:47:05 UTC+2, Mathias Ettinger a écrit
Using ansible 2.3.1.0 and the following playbook:
- hosts: localhost
tasks:
- debug: msg={{ vars }}
I get, amongst others: "ansible_os_family": "Archlinux", and
"ansible_distribution": "Archlinux",
What version are you using?
Le vendredi 21 juillet 2017 18:32:16 UTC+2,
t; me@host ~/Ansible> ansible-playbook arch-test.yml | grep ansible_os
> "ansible_os_family": "Arch Linux",
> "ansible_os_family": "Arch Linux",
> "ansible_os_family": &
release. It seems to be related to this. What's the best way to
> address this with the Ansible team? It's not a big issue but having no
> spaces in distribution or family name is a good practice.
>
> Thanks for your help, it's nice
You may be able to make this work with a simple:
- name test copy from variable
copy:
content: "{{ item.data }}
dest: "{{ target_dir }}/{{ item.filename }}'
with_items: "{{ mydict }}"
Why do You need an extra list?
--
You received this message because you are subscribed to the Googl
15 matches
Mail list logo
