Hello,
I have a Redhat 6.7 system with two versions of Python. The version that
came with the OS installation and used by the system (2.6) and a second one
that I installed (2.7.11). If I want ansible to use the 2.7.11 version,
what must I do to make that happen?
Can I still use "yum
But then all utilities/programs that rely on python will use the 2.7.11
version. I only wanted ansible to use it.
Thx
Al
On Wednesday, April 20, 2016 at 4:10:31 PM UTC-4, Mark Janssen wrote:
>
> As long as you make sure that your new version of python can be found
> first in the path, it
Any recommendations for problem related to this solution. If connectivity
to any one devices fails, then the registered variable (data) is not
accessible for any of the other devices that actually passed. This results
on the following error when the jinja2 template part of the playbook is
That was it Kia.. Thank you. I should have looked at your response more
closely. I missed that you had "data" as a child of hostvars. So is that
true in all cases any time you define a register variable? That variable
will be a child within hostvars?
Thank you again.
{{
hostvars[i] works because that is predefined variable in ansible. However
"data" is not. I tried data[i].facts.serialnumber but I get an error back
thats says data is undefined.
Thx
On Monday, March 20, 2017 at 3:51:37 PM UTC-4, Kai Stian Olstad wrote:
>
> On 20. mars 2017 20:10,
Hello,
I'm fairly new to Ansible and trying to do something very simple. I want
to collect a piece of information (version number) from a number a network
devices and generate a simple report.
- name: Get Data from devices
gather_facts: False
hosts: all
connection: local
roles:
Hello All,
Before upgrading the Ansible version is 2.1.2. After using yum to update
the Ansible package, the version still states 2.1.2?? What am missing? Did
I do something wrong here?
Thx
Al
[allan@SDNAUTOS02 ~]$ ansible --version
ansible 2.1.2.0
config file = /etc/ansible/ansible.cfg
Found the problem. This system actually has 2 versions of Ansible
installed . Does anyone know why the first one states the "python
version" but the second one does not?
[allan@SDNAUTOS02 my-ansible]$ /usr/bin/ansible --version
ansible 2.3.0.0
config file =
Thank you Jordan. I did not know you could set ansible_remote_tmp at the
task level. I will try that. As a work around before I saw your answer, I
just build a filter to return the md5 as follows:
- name: Calculate md5sum from local file
set_fact: qcow_md5sum="{{
Hello,
I'm having a problem where a particular task is failing when I use
delegate_to. The problem is I'm also setting ansible_remote_tmp to a
specific directory for the target systems. However, it appears that when I
use delegate_to: local, a local connection is setup and it wants to use
Hello,
I have a pretty simple playbook that has been working fine for a while.
It appears it can no longer connect via ssh to the device. Note, I can
manually ssh to the device with no problems. I ran the playbook with the
- option and here is the part of the output where the problem
Looks like it may be a different problem. I stripped the playbook down to
bare bones and it appears only the specific Vyatta commands no longer
work...
For example, this works (although the debug output still shows it
disconnects a couple of times but ultimately it works each time:
-
Hello,
I'm using the ios_facts module and trying to retrieve the configuration
from a Cisco CSR1000v. The configuration seems to be saved ok but the top
of the file contains two lines that are invalid configuration commands.
Thus, this file cannot be loaded into a router "as-is". The two
As a work around to this. After the config file is saved to Ansible server,
I used the lineinfile module to remove those 2 configuration lines. With
that being said, I still think this should be fixed unless someone has good
reason why those 2 lines should be left in the saved config file...
14 matches
Mail list logo
