it seems to have issues getting the device info, though the error is
pretty weird as in the current code 'm' is checked before accessing,
are you using an old version of ansible?
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" grou
We aren't doing anything special on our URLs at all. Attached is the output
of a keystone catalog. I would appreciate any feedback you might have on
any issues you see with the catalog.
As mentioned Vallard can provide access to a publicly available cloud for
testing purposes.
keystone catalo
for tower questions email supp...@ansible.com
--
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.
Hi Brian,
I am just talking about a standard output you get in the console when you
run ansible playbook. Here's the sample command:
ansible-playbook -i myinventory.yml my_playbook.yml
and the sample output:
GATHERING FACTS
***
ok:
Ah, thanks for the info on the security group stuff. I'll try that out.
I'm happy to let someone have a metacloud account to test things with.
On Fri, Sep 18, 2015 at 10:23 AM, David Shrewsbury <
shrewsbury.d...@gmail.com> wrote:
> Sorry you're having issues. Sounds like metacloud is doing somet
I have a playbook that goes over the nodes and gets the facts.
There is one node where this fails with following error.
Anyone got a Idea why this error happens?
Traceback (most recent call last):
File "/tmp/ansible/ansible-tmp-1442517427.38-239537369095604/setup", line
4471, in
main()
We were running 1.7.2, and are upgrading to 1.9.3-1. We install from git
(because we have some local mods to apply, which we've found easier to do
when installing via git), which means that we run .../hacking/env-setup,
and that seems to have changed between 1.7.2 and 1.9.3-1, in ways that
don't wo
Won't that cause the opposite problem when creating groups? Also I
believe the return is correct, it failed to delete the group as it is
not a local group and will still be present on the machine. We might
want to add a 'local_only' flag to both this and user to be more
specific on what you want as
Sorry you're having issues. Sounds like metacloud is doing something we
don't expect with
their endpoints since you are having the same problem. This is difficult to
debug without a
metacloud account.
Your solution to the image service problem was to add code to remove the
"/v1". Does that
solu
are you sure? try delegating a "shell: id" task
--
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.
Thought I included that in my original post but I didn't. Yes the user I am
logging in as is in the "nagios" group.
On Friday, September 18, 2015 at 12:48:05 PM UTC-4, Brian Coca wrote:
>
> So the user you login to the nagios server needs to be in the nagios
> group to write to the file.
>
>
>
So the user you login to the nagios server needs to be in the nagios
group to write to the file.
--
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
I found a solution to the problem
I added to ansible.cfg
[ssh_connection]
ssh_args = -o ControlMaster=no
--
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 ansi
Hi David,
of course! thank you very much!
I didn't recognized that the error message was only saying "ansible_mgt"
and not "ansible_mgt.ipv4.address"...facepalm
Regards,
Jost
Am Freitag, 18. September 2015 16:39:37 UTC+2 schrieb David Karban:
>
> Hi Josh,
>
> your idea is right:
> {% if ans
Hi Josh,
your idea is right:
{% if ansible_mgt is defined and ansible_mgt.ipv4.address is defined %}
server_address={{ansible_mgt.ipv4.address}}
{% else %}
server_address={{ansible_eth0.ipv4.address}}
{% endif %}
you have to check ansible_mgt first.
David
Linux server specialist/Specialista na s
Hi David,
the error message is:
fatal: [testserver.xxx] => {'msg': "AnsibleUndefinedVariable: One or more
undefined variables: 'ansible_mgt' is undefined", 'failed': True}
fatal: [testserver.xxx] => {'msg': "AnsibleUndefinedVariable: One or more
undefined variables: 'ansible_mgt' is undefined",
Hi,
I guess, in that case not even ansible_mgt will be defined? What is exact
error message (try ansible-playbook with -vvv) ?
David
Linux server specialist/Specialista na správu linuxových serverů
www.karban.eu
2015-09-18 15:50 GMT+02:00 :
> Hi everyone,
>
> one simple question and sry for my
Hi everyone,
one simple question and sry for my english skills :-)
I have a playbook with some templates, in one template I added a condition
to write a specific IP Address in my template.
(My servers have several network ports and unfortunately they have
sometimes different names. Ok, i could
Having the same problem with os_volume that I had with glance images where
I get a 404 error.
- Ansible 2.0 playbook:
- name: ensure there is a volume for storing data.
os_volume:
size: 40
display_name: lab_volume
register: vol
Error message:
fatal: [localhost]: FAIL
can you be more specific? give an example of what you are running and
trying to get.
--
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-
Windows 10
babun version 1.2.0
Vagrant 1.7.4
ansible 1.9.3
*First run*
{ Centos } » ansible testserver -s -m yum -a name=nano
-
<127.0.0.1> ESTABLISH
Hey everybody,
since I started using ansible 2.0 I've been having issues with this task:
- synchronize: src=/src/srcfile dest=/home/{{item}}/
remote_user: '{{item}}'
with_items:
- user1
- user2
with_items works fine for the dest parameter. It iterates through the
entire list.
I'm attempting to create an idempotent DB2 script runner using ansible. My
variables:
---
db2sql_hard_vars:
command_groups:
- description: first set of commands
dont_run_sql: 'select * from test'
commands:
-
sql: connect to master
Shouldn't that be ec2.results.instances instead of ec2.result.instances ?
--
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...@googlegr
Thanks for this.
There's a PR around for a re-write of the win_updates module which uses the
local scheduled task trick. The author of the PR was, if I recall,
reluctant to generalise it as he felt there were a lot of edge cases to
handle.
If you are willing to create a PR for your module peo
I think list is now a filter so perhaps try without the () on the end of
list
Not sure you can have {{ }} inside other {{ }} so maybe needs breaking into
two parts, set_fact to get the list of regex replaced play hosts and then
looking up the address from hostvars as a second step.
Hope that h
26 matches
Mail list logo
