I'm trying to understand the reasoning and address some of the problems
with the ansible and ansible-core split, in order to publishing workable
RPMs for the new ansible. Are the logs of the discussion or the analysis of
its purpose published anywehre?
I've been asking about this over
at
Thanks, that is a great help, I'll give it a try.
Also I stumbled across the product filter. Would it also work for this
issue? I tried to incorporate it into your example but haven't figured out
the syntax so far.
loop: "{{ common_vars | product( unique_vars )| list }}"
On Monday, November
Further to this I created a quick check for file playbook as below and it does
find it and displays the content successfully. So the copy script is just not
functional. Any ideas as to why it does not find the file?
- name: check if file exists
hosts: source server
gather_facts: true
Anyone know what this error means?
Port 9389 and port 5986 is open (tried test-netconnection from the server
from where the ansible command is being run from to destination server its
reporting below) :
The full traceback is:
Unable to contact the server. This may be because this server does
Thank you for the response. I made the change but still getting the same error.
Rene
From: dulhaver via Ansible Project
Sent: December 1, 2021 12:51 PM
To: ansible-project@googlegroups.com
Subject: [EXTERNAL *] Fwd: Re: [ansible-project] remote copy issue
as far as I am aware of things
as far as I am aware of things delegate_to is located above the module name
tasks:
- name: "copy "
delegate_to: destination server 1
copy:
src: /opt/odrive/alc/library/libraryusername.csv
remote_src: yes
dest: /var/alc
check_mode: yes
I am still
I am attemping o copy a file from one remote linux server to two remote linux
servers. My playbook is:
- name: copy file
hosts: "remote source server"
gather_facts: false
tasks:
- name: "copy "
copy:
src: /opt/odrive/alc/library/libraryusername.csv
remote_src:
thx @alex & Nico,
I did something quite similar (for one particular user).
As I am pushing a .bashrc up to the target anyway at some point I added my PATH
in the same manner you suggets here via the edit Module.
> On 12/01/2021 1:26 PM Nico Kadel-Garcia wrote:
>
>
>
>
> On Monday,
On Monday, November 29, 2021 at 3:17:19 AM UTC-5 ra...@linuxia.de wrote:
> On 26/11/2021 11:39, 'Roman Steinhart' via Ansible Project wrote:
> > Hi Stefan,
> >
> > probably with openssl or gpg.
> > See
> > https://gist.github.com/dreikanter/c7e85598664901afae03fedff308736b <
>
On Monday, November 29, 2021 at 12:20:12 PM UTC-5 alex...@gmail.com wrote:
> Traverse /home and for each user:
> edit:
> ~/.bashrc
> with:
> export PATH="SOMETHING":$PATH"
>
>
This way lies madness, and a stack of security issues when someone or some
process sticks alternative binaries or
On Tuesday, November 30, 2021 at 3:48:41 PM UTC-5 Nico Kadel-Garcia wrote:
> On Tue, Nov 30, 2021 at 11:39 AM David Moreau Simard
> wrote:
> >
> > Hi all,
> >
> > We're happy to announce that the Ansible 5.0.0 package has been released
> !
> >
> > Ansible 5.0.0 includes the newly
On Wed, Dec 1, 2021 at 3:11 AM Bond James wrote:
>
> Have some problem
> ansible --version
> ERROR! Unexpected Exception, this is probably a bug: module
> 'ansible.constants' has no attribute 'CONTROLLER_PYTHON_WARNING'
> the full traceback was:
>
> Traceback (most recent call last):
> File
just a wild guess ... could this mean the python3 package available on your
ansible controller is not recent enough for ansible 5.0 ?
> On 12/01/2021 9:11 AM Bond James wrote:
>
>
> Have some problem
> ansible --version
> ERROR! Unexpected Exception, this is probably a bug: module
>
Have some problem
ansible --version
ERROR! Unexpected Exception, this is probably a bug: module
'ansible.constants' has no attribute 'CONTROLLER_PYTHON_WARNING'
the full traceback was:
Traceback (most recent call last):
File "/usr/bin/ansible", line 76, in
if C.CONTROLLER_PYTHON_WARNING
14 matches
Mail list logo
