What if you don't place the vars file in a groups_vars subdirectory. What if
you place it in the directory of the playbook that runs the roles.
vars_files:
- my_vars.yml
Where my_vars.yml exists next to the playbook?
Walter
--
Walter Rowe, Division Chief
Infrastructure Services Division
Mobil
I removed the vars_file from my playbook.
I just double-checked and I am not loading iptables_v4_rules and/or
iptables_directory twice..
I wish I could throw it into a repo but this is on a non-Internet connected
device and can't be moved off.
I've moved from curious to frustrated.
On Tue
Do you still have that vars_files: thing? As Dick suggested, it feels like
that file is getting loaded more than once, and you don't want that.
Is it at all possible that variables iptables_v4_rules and/or
iptables_directory are being set anywhere else?
*[If you want to toss the whole thing in
Todd- thank you for clearing that up for me
I made default.yml all.yml amd reran things with the same errors.
I am running my roles from within a playbook like this.
- roles
- role1
become: true
- role2
become: true
On Tue, Feb 13, 2024 at 2:51 PM Todd Lewis wrote:
> This b
This bears repeating. I know I missed it the first few times I was told,
and then the light came on.
* All hosts are in the "all" group. (That much I got the first time. :)
* Any files /or directories/ in ./group_vars/ that match a host's
group names – including "all" – get loaded for that
On Tue, 13 Feb 2024 at 17:35, Kathy L wrote:
> When I make Todd's changes, I get the same original error EXCEPT it tells
> me CentOS is not a dict, even though I am targeting a Debian box.
>
> Dick, are you saying that the file all.yml in the group_vars folder does
> not need to be explicitly sta
The error appears to be in '/work/armory/roles/xxx/tasks/xxx.yml': line 266,
column 3, but may be elsewhere in the file depending on the exact syntax
problem.
The offending line appears to be:
- name: Save new iptables - IPv4
^ here
The error is being reported by a role.
Is the group_vars/d
When I make Todd's changes, I get the same original error EXCEPT it tells
me CentOS is not a dict, even though I am targeting a Debian box.
Dick, are you saying that the file all.yml in the group_vars folder does
not need to be explicitly stated in my playbook?
On Tuesday, February 13, 2024 at
On Tue, 13 Feb 2024 at 15:33, Kathy L wrote:
> Default.yml is at the playbook level in a folder called group_vars. It is
> being read in by my playbook like this:
>
> vars_files:
> - group_vars/default.yml
>
If 'group_vars' is adjacent to your playbook, then 'group_vars/default.yml'
would als
Hey Kathy,
I've been trying to reproduce the problem without success. However, I
think you've got one level of indirection too many going on. You have
iptables_directory:
CentOS: "/etc/sysconfig"
Fedora: "/etc/sysconfig"
Rocky: "/etc/sysconfig"
Debian: "/etc/iptables"
Ubuntu: "/etc/i
Does the same thing happen for all distros? Or only for Debian/CentOS, and
not for Rocky/Ubuntu?
--
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-proje
When I target CentOS I get this error:
The task includes an option with an undefined variable. The error was:
{'CentOS': '{{ iptables_directory[ansible_distribution] }}/iptables',
'Rocky': '{{ iptables_directory[ansible_distribution] }}/iptables',
'Debian': '{{ iptables_directory[ansible_distri
On Tue, 13 Feb 2024 at 14:22, Kathy L wrote:
> I've been working this issue for a week now. The code used to work
> perfectly and now it fails. Here is the error I get:
>
Logic dictates that something has changed. Did you upgrade anything? Or
otherwise make changes?
That would be the obvious th
I've been working this issue for a week now. The code used to work
perfectly and now it fails. Here is the error I get:
The task includes an option with an undefined variable. The error was:
{'CentOS': '{{ iptables_directory[ansible_distribution] }}/iptables',
'Rocky': '{{ iptables_directory[a
D'oh! Test one thing and post something else. *Argh!*
How about this:
- name: Save output to file
ansible.builtin.copy:
content: |
{{ output.stdout_lines[0:1] | join('\n') }}
dest: "show-output/{{ inventory_hostname }}.ios"
when output.stdout_lines is defined
On Monday, Marc
- name: Save output to file
ansible.builtin.copy:
content: |-
{{ '\n'.join(output.stdout_lines[0:1]) }}
dest: "show-output/{{ inventory_hostname }}.ios"
when output.stdout_lines is defined
On 3/13/23 11:13 AM, Merlijn De Wandel wrote:
Hi We have the following working config dow
Hi We have the following working config down below. However sometimes the
routers don't have the command "sh ip ospf nei" and we get the following
error:
FAILED! => {"msg": "The task includes an option with an undefined variable.
The error was: 'dict object' has no attribute 'stdout'\n\nThe erro
Hi,
Thanks for coming back. Yes, I added the debug task before this task and it
is printing correctly.
Now I managed to fix this issue by supplying the endpoint SG on the config
file which has the endpoints which is what it is expecting.
Thanks again.
On Tuesday, 15 June 2021 at 15:12:41 UTC
>From your mail , I can see vpc_endpoints is referenced
from stack_output_result.
SecurityGroupIds: "{{ *stack_output_result*
.net_stack_output_result.account_config.0.account_config.vpcs[stack_output_result.net_stack_output_result.account_config.1].app.
*vpc_endpoints*.security_group_ids|join(','
Below is the task
- name: create rxgt-ps-b2b-app-vpc-endpoints changeset
cloudformation_execute_changeset:
stack_name: "rxgt-ps-b2b-app-vpc-endpoints"
state: present
region: "{{
stack_output_result.net_stack_output_result.account_config.1 }}"
aws_access_k
Can you provide snapshot of what your task looks like?
On Tue, Jun 15, 2021, 6:22 PM kki...@gmail.com wrote:
> Hi All,
>
> I am trying to re-create the AWS Core infrastructure using ansible in
> another region. I am getting the following error
>
> The task includes an option with an undefined va
Hi All,
I am trying to re-create the AWS Core infrastructure using ansible in
another region. I am getting the following error
The task includes an option with an undefined variable. The error was:
'dict object' has no attribute 'vpc_endpoints'\n\nThe error appears to be
in
'/home/ec2-user/en
thx Vladimir this works to, but I already made this:
---
- hosts: servera
tasks:
- getent:
database: passwd
- name: lock
user:
name: "{{ item }}"
password_lock: yes
loop:
- uporabnik1
- uporabnik2
- uporabnik3
- uporabn
On Mon, 14 Dec 2020 06:37:05 -0800 (PST)
Jost Rakovec wrote:
> ... lock list of users on linux only if user exist
Try this
- name: Get passwd
getent:
database: passwd
- name: lock
user:
name: "{{ item }}"
password_lock: yes
loop: "{{ g
Hi
I would like to lock list of users on linux only if user exist, but have
some problems:
lock-user1.yml
---
- name: lock users
hosts: webservers
tasks:
- name: Check if user exists
getent:
database: passwd
key: "{{ item }}"
register: user_exists
i
Hi Dick Visser,
Thank you for your advice. I will try to sort this out. For more help I
will contact opnfv community.
Thanks & Regards,
Devakrishnan
On Wednesday, May 29, 2019 at 1:16:15 AM UTC+5:30, Dick Visser wrote:
>
> Did you get those playbooks from
> https://github.com/opnfv/apex/tree/m
Did you get those playbooks from
https://github.com/opnfv/apex/tree/master/lib/ansible/playbooks ?
If so, just a link would have been sufficient, rather than copy pasting
them as an unreadable piece of HTML email.
In any case, those playbooks are part of a much larger set of playbooks and
code. Th
Hi @ansible folks,
Recently I found an Ansible error while installing Opnfv-Apex. I'm getting
the below error message while deploying. It seems to be Ansible playbook
failed error.
*Error Message :*
*2019-05-27 20:45:16,635 INFO: TASK [include_tasks]
*
The error is caused earlier on, namely in the task where you register
auditd_result.
Try debugging that.
On Thu, 27 Apr 2017 at 23:12, Alicia Smith wrote:
> Hello, I was wondering if I could get some help on determining what is
> wrong here.
>
> This worked prior to 2.2.x
> Now when I run it
Hello, I was wondering if I could get some help on determining what is
wrong here.
This worked prior to 2.2.x
Now when I run it I get the following error:
fatal: [redacted-host.com]: FAILED! => {"failed": true, "msg": "The
conditional check 'auditd_result.stdout.find(\"audit-2.3\") != -1' faile
I'm a bit stumped here.
I have a playbook setup that uses hostvars to fill in expressions in other
places including jinja2 templates. Whenever one of those variables is an
IP address, I get the error 'dict' object has no attribute 'xx.xx.xx.xx'.
when there's a var set to that value.
For examp
31 matches
Mail list logo