[ansible-project] Re: Role Handler Separation

2024-02-09 Thread Daniel Barros
Would something like that help? --- - name: Playbook Temp hosts: localhost gather_facts: true vars: restart_svcs: Debian: Restart Debian service RedHat: Restart RedHat service handlers: - name: Restart Debian service ansible.builtin.debug: msg: "some debi

Re: [ansible-project] rescue for target failed connection question using localhost

2023-08-21 Thread Daniel Barros
Hi Brian. Using ignore unreachable and failing based on the condition of the register variable based on your example did the trick for me. I appreciate your time and sharing. Br On Mon, Aug 21, 2023, 15:26 Brian Coca wrote: > I forgot to mention, the reason your rescue does not work is because

[ansible-project] rescue for target failed connection question using localhost

2023-08-21 Thread Daniel Barros
Hi everyone. Good day. When we have a regular task like creating a file, or something similar, we can use block and rescue to manage what happens in failure cases. But can we do the same for the first task (connection) on a target and rescue using localhost? What I would like to achieve is thi

[ansible-project] Ansible Async List will not use same retrying for batch

2022-12-09 Thread Daniel Barros
Hi everyone, how are you doing? I have a conceptual question that I would like your comments if possible. I’m using async with poll 0 on a loop. Something like this *async: 45* *poll: 0* *with_items: "{{ big_list }}"* Let’s say this loop has 50 commands. All the commands are started almos

Re: [ansible-project] Question about community.general.opentelemetry callback

2022-11-08 Thread Daniel Barros
lback to work with that version. (It removed some helper function > that the plugin was using, see > > https://github.com/ansible-collections/community.general/blob/stable-5/CHANGELOG.rst#bugfixes > .) > > Cheers, > Felix > > > > > On Mon, 7 Nov 2022 18:15:36 -030

Re: [ansible-project] Question about community.general.opentelemetry callback

2022-11-07 Thread Daniel Barros
. >> I don't know what it could be then. >> >> On Mon, 7 Nov 2022 at 10:58, Daniel Barros >> wrote: >> >>> Hi man. >>> >>> This is the entire output >>> >>> ansible --version >>> ansible [core 2.13.2] >>&

Re: [ansible-project] Question about community.general.opentelemetry callback

2022-11-07 Thread Daniel Barros
1.2 libyaml = True On Saturday, October 29, 2022 at 12:49:36 PM UTC-3 dnmv...@gmail.com wrote: > On Fri, 28 Oct 2022 at 17:23, Daniel Barros wrote: > >> Hi man, thanks for the time. >> >> Please see the information as requested >> >> ansible --version >>

Re: [ansible-project] Question about community.general.opentelemetry callback

2022-10-28 Thread Daniel Barros
wrote: > What does 'ansible --version' say? > And 'pip --version' > > > > On Fri, 28 Oct 2022 at 16:58, Daniel Barros > wrote: > >> Hi group, good day, how are you? >> >> >> >> I have a question about using community.gen

[ansible-project] Question about community.general.opentelemetry callback

2022-10-28 Thread Daniel Barros
Hi group, good day, how are you? I have a question about using community.general.opentelemetry to send data to APM. I have set my ansible.cfg like this. [defaults] callbacks_enabled = community.general.opentelemetry [callback_opentelemetry] enable_from_environment = ANSIBLE_OPENT

Re: [ansible-project] Understanding block and rescue

2022-08-18 Thread Daniel Barros
Hi, I believe I replied only to the author, so sorry if anyone is seeing duplicated messages from me. But try moving the task that failed inside the block. Its currently outside --- - block: - name: "status systemd-resolved" command: systemctl status systemd-resolved register: re

Re: [ansible-project] Ansible 2.13 yum module - requires minimum version of target python of 2.7 or 3.5. But I already have that

2022-08-08 Thread Daniel Barros
he last version of ansible-core to support Python 2.6 for target > execution was ansible-core 2.12. > > On Fri, Aug 5, 2022 at 4:42 PM Daniel Barros > wrote: > >> I have an Ansible (2.13) machine targeting a remote centOS 6 with Python >> 3.6. >> >> Remote m

[ansible-project] Ansible 2.13 yum module - requires minimum version of target python of 2.7 or 3.5. But I already have that

2022-08-05 Thread Daniel Barros
I have an Ansible (2.13) machine targeting a remote centOS 6 with Python 3.6. Remote machine has python3.6 installed and variables are set like this: $ ansible-inventory --host centos-6-vm { "ansible_private_key_file": "~/.ssh/id_rsa", "ansible_python_interpreter": "/usr/bin/pytho