Hi Markus,
No, sorry. I haven't tried to sort it out as I was able to reduce the size
of the files I transfer. I guess, it's something the ansible team should
take care of.
Cheers,
Jacek
2017-02-14 15:46 GMT+00:00 Markus Huber :
> Jacek, could you figure this issue out? Seems
FYI, I am seeing that on AWS as well. Very intermittent but happens every
50 deployments or so for us.
In our case it's all Debian running against other Debian machines all
within AWS.
On Monday, August 22, 2016 at 11:41:24 AM UTC-7, Aaron Bernardino wrote:
>
> Thanks for the feedback. I tried
So basically I will need to set facts for every major playbook once it
succeeds and then check for it?
I thought Ansible was idempotent in this way by default
On Saturday, August 20, 2016 at 3:28:45 AM UTC-7, Dick Davies wrote:
>
> Use a when: clause, or make the included files tasks idempotent.
Short version:
Why does Ansible keep running '-include: mysql-cluster.yml' whenever it
encounters it? Can't it recognize this was already executed once?
Long version:
I am trying to find a good way to organize Ansible scripts so that they
meet these requirements:
- Developers can run their proje
Short version:
Why does Ansible keep running '-include: mysql-cluster.yml' whenever it
encounters it? Can't it recognize this was already executed once?
Long version:
I am trying to find a good way to organize Ansible scripts so that they
meet these requirements:
- Developers can run their proje
Just to give a little more insight. I cut the size of my 'eSC-store-.tgz'
file down to 396MB and exactly the same code works fine. It must be
something with the size, then.
Best,
Jacek
--
You received this message because you are subscribed to the Google Groups
"
h the storage blob
fetch: src={{ dump_file.stdout }} dest={{ dump_directory
}}/eSC-blobStore.tgz flat=yes
---
I'm using version: ansible-playbook 1.9.0 (stable-1.9 22b10a8f6e)
Any help appreciated,
Jacek
--
You received this message because you are subscribed to the Google Groups
&qu
I always worked with sources straight from github. Previously, it worked
with 1.7.? (can't remember exactly) then, sometime in Feb or earlier, I
updated to 1.9 (ffb281d96c) and it was ok, too.
W dniu czwartek, 19 marca 2015 15:17:40 UTC użytkownik Brian Coca napisał:
>
> I'm looking at the previ
-init
- { role: esc-db, sudo_user: postgres }
That's more hassle than it was previously... Is this going to be supported
again? I've been using this play for about half a year, so it's only
relatively recent change.
Jacek
W dniu czwartek, 19 marca 2015 13:45:24 UTC użytkowni
k
command: /usr/bin/whoami
sudo_user: postgres
register: first_task
- debug: var=first_task.stdout
- name: Second task
command: /usr/bin/whoami
register: second_task
- debug: var=second_task.stdout
--
Best,
Jacek
W dniu środa, 18 marca 2015 15:46:14 UTC uż
Sorry, I need to leave now but will get back to you with an example later
today.
Cheers,
Jacek
W dniu środa, 18 marca 2015 14:59:46 UTC użytkownik Brian Coca napisał:
>
> same result if host is localhost, i can reproduce the issue with roles
> not picking up sudo_user but not wi
What do you mean by 'show test'?
Did you try when the target machine (your 'testmachine') is set to
localhost in the inventory?
W dniu środa, 18 marca 2015 14:41:34 UTC użytkownik Brian Coca napisał:
>
> can you show test with the issue at the play level? i cannot
> reproduce, i used the followi
set at the task level too, it's correct:
---
"[sudo via ansible, key=zprftkljnlzogwijomrqivtiiebwqqqs] password: " -u
postgres /bin/sh -c
---
Jacek
W dniu środa, 18 marca 2015 14:10:38 UTC użytkownik Brian Coca napisał:
>
udo_user: postgres' set at the playbook level
isn't properly passed down to the role.
The problem doesn't appear on an earlier version: "ansible 1.9 (devel
ffb281d96c) last updated 2015/03/03 19:12:13 (GMT +100)"
Any help appreciated.
Cheers,
Jacek
--
You receive
g: The requested domain name is not accessible with this api_key; try
using its ID if known.
FATAL: all hosts have already failed -- aborting
PLAY RECAP
to retry, use: --limit @/home/jacek/dns.retry
localhost
Great, thanks!
Jacek
2014-11-04 4:10 GMT+00:00 Brian Coca :
> using delegate_to: localhost, local_action or connection: local with
> file/copy/template should do the trick
>
> On Mon, Nov 3, 2014 at 7:42 PM, Jacek wrote:
>
>> Hi,
>>
>> Is there a way to ask
more details. I use ansible to deploy my service on a
remote cluster and once it's deployed I need to upload various bits and
pieces to it. The property file is used to identify the service endpoint
address.
Cheers,
Jacek
--
You received this message because you are subscribed to the G
Ok, after a little search I've got it; for anyone interested:
- set_fact: address_variable={{ item }}
with_items: groups.server
when: "'server' not in group_names"
Cheers,
Jacek
W dniu piątek, 19 września 2014 14:06:25 UTC+1 użytkownik Jacek napisał:
>
>
Thanks James,
That's nice. One thing I'm not sure about is the 'server_address_here'
which you wrote. Ideally, what I need there is the name/address of the
first (and the only) host in the inventory group 'server'.
Is there a way to do this?
Cheers,
Jacek
W d
cludes many places with such a reference, so
I thought about first setting the server address variable, and then using
this variable to evaluate the template. Is this correct way of thinking?
How can I set a variable in a play before template evaluation? Otherwise,
have you got any other ideas?
Che
ork in the legacy mode. In effect, this means I need to set
priorities manually during service installation because the LSB init header
gets ignored.
Best,
Jacek
W dniu piątek, 12 września 2014 15:28:28 UTC+1 użytkownik Michael DeHaan
napisał:
>
> "The trouble is that in my case
Thanks Michael for suggestion.
The trouble is that in my case there seem not to be any other way than
stating priority manually during service installation (as in the given
example). I think the quickest (dirty) approach is to run a command to
install the script.
Thanks anyway,
Jacek
W
ppreciated.
Cheers,
Jacek
--
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 to this group, s
I use current version:
$ ansible --version
ansible 1.4
PS. I somehow missed your response.
W dniu poniedziałek, 25 listopada 2013 19:45:02 UTC+1 użytkownik Michael
DeHaan napisał:
>
> What is "ansible --version" ?
>
>
>
>
> On Sun, Nov 24, 2013 at
My playbook consists of two steps:
- Setup remote user (one of possibly many), and do stuff that require
root
- Login to this user and do rest without privileges
It seems that synchronize module doesn't play well with it. It seems that
it tries to login to ansible_ssh_user despite
25 matches
Mail list logo