Hi all, we're very happy to announce that Ansible 2.2.1 RC1 is ready for
testing!
Some bug fix highlights:
* Fixes a bug where undefined variables in with_* loops would cause a task
failure even if the when condition would cause the task to be skipped.
* Fixes multiple bugs related to
- name: Configure remote device.
vyos_config:
lines:
- set service snmp community testing authorization ro
provider: "{{ cli }}"
This works exactly as intended when I try it running Ansible 2.2 from a
CentOS control machine to a VyOS 1.1.17 node that was
oops .. I missed.
Now I have corrected like below ... still bad luck with me ... . Also If I
executed these commands directly into clients servers and its working.
- name: Subscribing a new channel
shell: sh -c "sudo yum clean all"
- shell: sh -c "sudo rhnreg_ks --activationkey
I searched and couldn't find anything saying one way or the other but I am
trying to basically build a bunch of Coreos VMs(just for lab and practice)
using ansible. I can deploy them just fine but I would like to do what I do
in powershell and modify the guestinfo to provide Coreos with its
On 18. nov. 2016 16:16, stack...@gmail.com wrote:
Added like below , still am getting error :(
Have you read the error message?
- name: Subscribing a new channel
shell: sh -c "rhnreg_ks --activationkey 1-vblock20161026"
- name: Subscribing a new channel forcefully
shell: sh
Added like below , still am getting error :(
- name: Subscribing a new channel
shell: sh -c "rhnreg_ks --activationkey 1-vblock20161026"
- name: Subscribing a new channel forcefully
shell: sh -c "rhnreg_ks --activationkey 1-vblock20161026 --force"
TASK [I am waiting for
On 18. nov. 2016 12:49, stack...@gmail.com wrote:
- name: Subscribing a new channel
shell: sh -c "rhnreg_ks --activationkey 1-vblock20161026"
shell: sh -c "rhnreg_ks --activationkey 1-vblock20161026 --force"
One task can only have one module.
You can add a "- name" to the last
Hi,
I have two testing environments, located in different regions. Within each
of those environments, among all the servers, there is a monitoring server.
In one of my ansible roles I would like to be able to select the ip address
of the relevant monitoring server. I thought that I could use a
Ansible version is ansible-2.1.1.0-1
On Friday, November 18, 2016 at 6:22:05 PM UTC+5:30, stac...@gmail.com
wrote:
>
> Any idea about the below error -
>
> [sysadm@pclprdftsnsoft1 ~]$ ansible-playbook 2.yml
> [WARNING]: While constructing a mapping from /home/sysadm/2.yml, line 14,
>
Any idea about the below error -
[sysadm@pclprdftsnsoft1 ~]$ ansible-playbook 2.yml
[WARNING]: While constructing a mapping from /home/sysadm/2.yml, line 14,
column 6, found a duplicate dict key
(shell). Using last defined value only.
PLAY [patch]
Dear Team
First i wish you good morning
I am new engineer in ansible field, about linux i have good knowledge but i
got project of ansible time complition is very short time. i am feeling too
much happy with ansible feature.
now i am sharing my issue which i am facing
I have setup ansible
I have some question about the ansible 2.3 roadmap of Networking as below
blue:
*Networking*
- Persistent connection manager è Does it supported by openssh?
- Netconf/YANG implementation (only feature) è We now using ncclient
as netconf lib, does it work ok now?
-
is posible confugure LDAP and not Kerberos?
El martes, 15 de noviembre de 2016, 15:59:05 (UTC+1), Aitor Gómez escribió:
>
> ok.. works when i execute in ansible (whit local user)
>
> But in Tower not works i will check again the Tower configuration
>
>
>
>
> El martes, 15 de noviembre de
Hi all,
I am trying to do
- name: Check if package-1 is installed
command: dpkg-query -l package-1
register: deb_check
ignore_errors: yes
- name: Check that package-1 designated ports are free
wait_for: port={{ item }} state=absent timeout=10
with_items:
14 matches
Mail list logo
