Re: [ansible-project] Re: ERROR! 'with_ldap' is not valid attribute for a Task

Since those look like plugins (and not modules) - copy the files from filter_plugins and lookup_plugins to the directories in your setup (if you don't have those dirs create them at the same level as your playbook). kind regards Pshem On Sat, 22 Jul 2017 at 00:10 Grzegorz Sz.

Re: [ansible-project] What do the verbose levels enable in Ansible?

There are really no specific names or thresholds, they just give increasing information as you add v's, for example tracebacks are shown with 3, but there is no formal list as each subsystem adds what made sense to the programmer at the time. -- -- Brian Coca -- You received this

Re: [ansible-project] Ansible modifies PYTHONPATH which causes Python commands to fail

I'm not sure I understand... Are you pointing out the PYTHONHOME environment being set? If so, that's not something that ansible sets on its own. It seems like you have it set on the remote host or are telling ansible to set it inside of a playbook or role. For instance, through the

[ansible-project] Ansible 2.4 Freeze Dates

Hello folks, Just a heads up! We have solidified the release schedule for the next version of Ansible. For those interested, the roadmap for the next version can be found here . Core Engine Freeze and

[ansible-project] Change in location of Ansible packages

In order to align better with Red Hat processes, the Ansible team will be making some changes in how Ansible packages are distributed to the community. For users of RHEL/CentOS/Scientific Linux version 7, the Ansible package will transition from the EPEL repository to the Extras channel.

[ansible-project] Archlinux OS Family issue

I'm testing Ansible roles with Archlinux and one of them uses ansible_os_family to include variables or tasks. So I have: - name: include OS vars include_vars: "{{ ansible_os_family }}.yml" when: ansible_os_family == 'Archlinux' Problem is that ansible_os_family gets 'Arch Linux' as value,

[ansible-project] Using Pathword Authentication to run a Playbook

Hello! I have a single playbook that with various plays in it. It goes out to different environments, either dev, uat, or prod (based on the --extra-vars input by the user deploying the playbook). i.e. ansible-playbook -i hosts deploy.yml --extra-vars "env=uat" Is there anyway I can set

Re: [ansible-project] How to *not* print ansible diagnostic error messages?

Hi On 07/21/2017 05:17 PM, Branko Majic wrote: On Fri, 21 Jul 2017 16:34:53 +0200 Frank Thommen wrote: Hi, I have a playbook which executes a local task from which I need the exit status in later steps: - name: Get exit status of ./run.sh local_action:

[ansible-project] Ansible "file" module and attributes in 2.3.1.0

I've got a set of systems that have a configuration file with the "immutable" flag set on them by a previous setup process. The "lsattr /etc/security/access.conf" on a RHEL 6 system shows the "i" flag set. Manually doing a "chattr -i /etc/security/access.conf" removes the flag, but I'd like

Re: [ansible-project] How to *not* print ansible diagnostic error messages?

On Fri, 21 Jul 2017 16:34:53 +0200 Frank Thommen wrote: > Hi, > > I have a playbook which executes a local task from which I need the > exit status in later steps: > > >- name: Get exit status of ./run.sh > local_action: command ./run.sh > register:

[ansible-project] How to *not* print ansible diagnostic error messages?

Hi, I have a playbook which executes a local task from which I need the exit status in later steps: - name: Get exit status of ./run.sh local_action: command ./run.sh register: ES ignore_errors: yes - name: Do something if ./run.sh failed command:

[ansible-project] Ansible Silo - Ansible in a 100% controlled environment

Fellow Ansible users, I'd like to bring to your attention the release of Ansible Silo. Ansible Silo is a drop-in replacement for Ansible packing Ansible with all it's dependencies into a docker image. The main features: 1. Self-contained environment. No Python, no modules required. The

Re: [ansible-project] /etc not writable

Try these options Copy the file to the sudo user's home directory or any other directory where the user has got permission. Or Increase the permissions of the destination directory so that user can write into that directory. Fayad Sent from my OnePlus One On 21-Jul-2017 6:33 PM, "Yuriy

Re: [ansible-project] Loop using with_items twice

Yes thats exactly what I wanted to do but I thought I had to use with_items at the bottom to provide the list that it would loop through. Thanks > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop

Re: [ansible-project] /etc not writable

Hello. I have similar case, and i get this error, but i do need to create it as sudo user. I do not have root privilege. Can someone please advise? Thank you On Friday, May 6, 2016 at 11:44:08 AM UTC-4, Kai Stian Olstad wrote: > > On 06. May 2016 14:46, Sanjay Kumar wrote: > > I am not able

Re: [ansible-project] Loop using with_items twice

On Thu, 20 Jul 2017 18:49:55 -0700 (PDT) Anfield wrote: > What is the correct way to use with_Items to loop over two files? The > playbook is failing at the 2nd task > > Getting an error - TASK [Create users from vars users] >

[ansible-project] Re: ERROR! 'with_ldap' is not valid attribute for a Task

I try to use module from : https://github.com/quinot/ansible-plugin-lookup_ldap BR Greg On Friday, July 21, 2017 at 9:08:50 AM UTC+2, Grzegorz Sz. wrote: > > Hi, > > I use 'with_ldap' role from lookup_module. It seems that my playbook > doesn't see it. There is an error: > > ERROR! 'with_ldap'

Re: [ansible-project] ERROR! 'with_ldap' is not valid attribute for a Task

Hi, I'm not sure which module you're referring to, but in your playbook you use 'debug' module. Also the 'with_ldap' section is not indented correctly - if it's a parameter to a module it has to be indented more then the name of the module you're using. kind regards Pshem On Fri, 21 Jul 2017

[ansible-project] Ansible modifies PYTHONPATH which causes Python commands to fail

Ansible appears to modify PYTHONPATH internally to vendored versions of some modules. This causes Python scripts executed within playbooks to potentially fail if there are module conflicts. []# ansible-playbook -e "*ansible_python_interpreter=/usr/bin/python*" -vvv test-Sonan3.yml Using

[ansible-project] Re: tagging in ec2_elb_lb and ec2_asg :-(

The solution for you is to use your variable ec2_tags as list entry with the module ec2_asg. This looks like this (rest of the arguments not shown): - name: Create Load Balancer ec2_elb_lb: name: "{{ elb_name }}" #other args tags: "{{ ec2_tags }}" - name: Create Autoscaling

[ansible-project] Re: tagging in ec2_elb_lb and ec2_asg :-(

> > The solution for you is to use your variable ec2_tags as list entry with > the module ec2_asg. > This looks like this (rest of the arguments not shown): - name: Create Load Balancer ec2_elb_lb: name: "{{ elb_name }}" #(...) tags: "{{ ec2_tags }}" - name: Create

[ansible-project] ERROR! 'with_ldap' is not valid attribute for a Task

Hi, I use 'with_ldap' role from lookup_module. It seems that my playbook doesn't see it. There is an error: ERROR! 'with_ldap' is not valid attribute for a Task Can anybody help me, please ? My task: - name: List group members debug: msg: "group member {{ item }}" with_ldap: -