Not used 1.7, only 1.9. And my experience is that only variables defined on
defaults/main.yml on dependant role can be overridden. I usually use
group_vars to override them, but in a few corner cases the only way I found
to achieve what you pretend to do is to override them at the playbook
level,
Thank you! Can you point me to the documentation somewhere, where this is
clarified?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi all.
I have role_a and role_b which depends on role_a.
role_a defines variable var_foo (in vars/main.yml), role_b wants to
redefine it (in its own vars/main.yml). With 1.7.2 this works, but with
1.9.[24] - not.
I've tried to pass required variable through meta (- {role: role_a,
var_foo:
I have notices that if I use a Jinja2 variable in the YAML map key, it's
not substituted by the variable's value as in the array and the map value.
For example if I have the following playbook:
---
- name: Test play
hosts: all
connection: local
gather_facts: no
vars:
test_var: aaa
Hello, i tried some playbook runs with an without paramiko. There ist
always the same problem and i think that the module ansible-playbook has th
root cause. I use the same user in the ssh and the cron session so the
privileges on the remote host are the same. May be my local environment is
I changed the first script to :
*- hosts: JMETER_REMOTE_VM sudo: True user: simsu gather_facts: False
tasks: - command:
/usr/local/jmeter/apache-jmeter-2.13/bin/start_jmeter.sh args:
chdir: /usr/local/jmeter/apache-jmeter-2.13/bin/*
still doesn't start jmeter on remote
Try shell: instead, you might need that.. Also make sure it's executable..
(Stating the obvious) ..
Alex
On 26 Jan 2016 8:00 a.m., "Christophe Dumont"
wrote:
> I changed the first script to :
>
>
>
>
>
>
>
>
> *- hosts: JMETER_REMOTE_VM sudo: True user: simsu
Hello, i try to run an ansible playbook every day and i use cron.
i get the following error:
+ sshpass -p x ansible-playbook -i all_actual_sp3_hosts.txt
uk_key.yml --ask-pass -c paramiko
Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 323, in
its correct way to reference most vars
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post
also it will be helpful if you post the output of the task
On Tue, Jan 26, 2016 at 3:32 AM, Alex Leonhardt wrote:
> Try shell: instead, you might need that.. Also make sure it's executable..
> (Stating the obvious) ..
>
> Alex
>
> On 26 Jan 2016 8:00 a.m., "Christophe
Thanks for clarifying this Brian.
Dave
On Tuesday, 26 January 2016 06:57:54 UTC-8, Brian Coca wrote:
>
> its correct way to reference most vars
>
>
> --
> Brian Coca
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from
Ok, so the problem I'm having in making this a callback is that I want to
open a ticket on playbook start and close it on stats.
In order to open the ticket, I need certain information that will be
specific to the playbook being run. The only way I can find to pass vars is
through play_vars,
Hi
I have the bellow template stored under the shared role but it's been
deployed by other roles as in our web role in our example :
# roles/shared/templates/config.conf.j2
#roles/web/taks/main.yml :
- name: deploy config
template: src=config.conf.j2 dest=/etc/project/config.conf
In
Hi,
Lets say I have a playbook with two plays and the first one determines the
hosts on which the second play should run. For instance, lets assume the
first play is a local play that has one task. The task runs a script and
its output provides the server(s) that the next play should run in.
Perhaps you should provide the details of the playbook as well here. There
are many possibilities. For example, this can happen due to the ssh user in
the cron. When you run the playbook in a ssh session, you are running with
you as the logged-in user. The cron user must have similar privileges
Perhaps you should provide the details of the playbook as well here. There
are many possibilities. For example, this can happen due to the ssh user in
the cron. When you run the playbook in a ssh session, you are running with
you as the logged-in user. The cron user must have similar privileges
Hi,
For plays, the "hosts" element accepts multiple hosts separated by colon.
That is,
hosts: "host1:host2:host3"
- works. However, within a task, when delegating to other hosts, the same
pattern does not seem to work. That is,
delegate_to: "host1:host2:host3"
- doesn't appear to work. I
Looking forward to this patch!
For those testing vmware, i've added a few features to vmware.py dynamic
inventory which ec2.py inventory comes with but were sorely missing in
vmware.py.
instance_filters and --refresh-cache. Plus a bug fix that allows cache_dir
to be found.
I tried on multiple amazon linux hosts, both using native python 2.7.10 as
well as a virtual environment for python 2.7.10. I have also tried with
Ansible 1.9.4 and 2.0.0.2, and with boto 2.38.0 and 2.39.0. The same error
persists:
failed: [localhost] => {"failed": true, "parsed": false}
Thanks, I also arrived at the same conclusion.
@ivanelson
[]s
2016-01-26 1:27 GMT-03:00 Brian Coca :
> even when noninteractive is passed, it can prompt for answers, try
> running manually and see what the question is, debconf can be used to
> set the answer ahead of time and
20 matches
Mail list logo