Yeah me neither, will have a look tonight, we can't just throw/raise an
ansible error right?
--
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
>
> It appears there are now about 12 other commits in there, so the best
> thing to do would be to resubmit this as a squashed patch containing just
> the one commit.
>
Have done so: https://github.com/ansible/ansible/pull/8406
With 160 P3 pull requests, it seems ansible is successful!
Didn'
TASK: [name | Copying Build to local host]
warning: md5sum command failed unusually, please report this to the list so
it can be fixed
command: [u'(/usr/bin/md5sum
/var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)',
u'(/sbin/md5sum -q /va
For those interested there are some questions about cloud and config
tooling (cough, Ansible, cough) should you be interested:
https://www.surveymonkey.com/s/Q5YC2NF
Warning: somewhat long
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To
Can you try this on the development branch?
We've recently applied some patches to clean up inventory that should
address this problem when using multiple inventory files at once.
1.7 is due for release soon, so it's pretty much set to go.
On Fri, Aug 1, 2014 at 6:34 PM, wrote:
>
> Let me as
I'd be open to a param on the fail module for that.
Not entirely sure what the plumbing throughout the stack might be to get it
done.
On Fri, Aug 1, 2014 at 4:21 PM, Outsider wrote:
> Maybe a fail_all module or a modification of the current fail module to
> add an all argument?
> On 1 Aug 20
Let me assume that we have a inventory file called hosts:
hosts
[openstack]
keystonec
sproxyc
snode01c
snode02c
snode03c
keystone
sproxy
snode01
snode02
snode03
and a dev inventory file
[dev]
keystone
sproxy
snode01
snode02
snode03
I have a test.yml file
---
- hosts: openstack:&dev
tas
Maybe a fail_all module or a modification of the current fail module to add
an all argument?
On 1 Aug 2014 22:17, "Outsider" wrote:
> This got me thinking that we kinda need an action to mimic
> any_errors_fatal in a task, would be very helpful in cases like this..
> where you need to trigger a w
This got me thinking that we kinda need an action to mimic any_errors_fatal
in a task, would be very helpful in cases like this.. where you need to
trigger a whole playbook failure conditionlly without affecting the default
failure behavior.. anything like that in the works?
On 1 Aug 2014 22:08, "M
Another nice shortcut that is a bit of syntactic sugar for "fail + when" is
the assert module. It's a little weird because it has the "that" in there
but we needed a key name for the argument.
- assert:
that:
- "confirmation == 'YES'"
OR:
- assert: { that: "confirmation == 'YES' }
e
Hi,
FYI - You're replying to a thread that is almost a year old.
It sounds like you have a new issue, but I'm not sure what version of
ansible you are running.
Please let us know this and what OSes you have on both sides of the
equation for starters, and we can go from there.
On Fri, Aug 1,
Hmm, the nesting seems interesting and is not something we'd usually
recommend, but if you can keep it straight, yay.
You might consider just using the copy module to copy over the template,
and then creating on the other a "vars" file using a template, and then
letting it run as normal.
But I am
Calling lineinfile without any other arguments like my example would insert
the lines at the end of the file if they don't already exist.
You can modify this behavior using insertbefore and insertafter, both take
regex as a value, so you can determine certain sections to add the new
lines to.. us
I forget what other network issues could exist at this time, though should
be able to discover from general network and SSH type debugging.
(Make sure you turned off that check on the remote, not the control
machine, if not already)
On Fri, Aug 1, 2014 at 3:44 PM, Tiglath wrote:
>
>
> Thank
If you just call lineinfile, where will it write them? At the end? What
if your target file has some kind of terminator, can you do a blanket
insertbefore or insertafter? I'm not really grokking the concept of
'backrefs'.
On Friday, August 1, 2014 11:33:36 AM UTC-7, Amr Ali wrote:
>
> You
Thank you for your replies.
I just tried that, no effect. Turned on pipelining, same.
It does seem like a 30 sec or so wait at least before it transfers each
file.
It's not useless, but it's going to slow playbook development.
On Friday, August 1, 2014 2:47:21 PM UTC-4,
Dozens of lines to the audit log configuration.
I probably will just push a script and run it. But you're right... it's
"un-ansible-like" :-)
But so long as our scripts can be run idempotently, it isn't a total hack
:-)
On Friday, August 1, 2014 11:35:00 AM UTC-7, Mike Ray wrote:
>
>
>
> Out
My thought might be you are running things with an inventory file that is
not in /etc/ansible, so it's looking for a host_vars directory beside that
inventory file.
Other than that I don't know what might be up...
On Fri, Aug 1, 2014 at 10:52 AM, Piet83 wrote:
> Of course:
>
> ansible-vault
I have seen reverse DNS lookup issues before, that can be a thing, so +1
Greg!
If using SSH without ControlPersist do also turn on pipelining.
On Fri, Aug 1, 2014 at 2:47 PM, Greg Andrews wrote:
> In the past, I've seen ssh connections into Solaris machines take a long
> time because the Sola
First of all failed_when doesn't work for vars_prompt only for tasks..
here is what you could do :
- hosts: all
any_errors_fatal: yes
vars_prompt:
name: "confirmation"
prompt: "Are you sure you want to run this playbook? Answer with 'YES'"
default: "NO"
private: no
tasks:
In the past, I've seen ssh connections into Solaris machines take a long
time because the Solaris ssh daemon was doing a reverse DNS lookup on the
connecting machine and there was no DNS for the machine. 30 seconds later,
the DNS lookup timed out, and the connection continued.
If you have root on
How do you set up a confirmation prompt before running a playbook?
I'd like to have to enter "YES" before the playbook makes any changes to
hosts. Right now I have the following code in site.yml, but it's not
working.
vars_prompt:
- name: "confirmation"
prompt: "Are you sure you want to
When I run ansible-playbook in accelerate mode and for some reason ansible
task fail the next run will not connect with following error
PLAY [all]
GATHERING FACTS
*
I've also run into this issue and haven't picked the best way to deal with
it yet.
You can always run that command via the shell module. Occasionally commands
get a little gross and you'll have to add so many escape characters and
quotes that even you can't tell what's going on. If that happens
You can use lineinfile and with_items
Ex:
- name: Add lines
lineinfile: dest=/some/file line={{ item }}
with_items:
- "add a line"
- "another line"
- "and so on"
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubsc
Can't take any credit, I'm just a very content user is all. Good luck with
your PR.
On Fri, Aug 1, 2014 at 5:00 PM, Ned McClain wrote:
> Michael, Stephen,
>
> I appreciate you taking the time to respond to this old thread, and for
> your thoughts, and for all your hard work on Ansible.
>
> I wi
I have a list of lines I want to add to a file on the target system if they
don't exist. I don't want to wholesale overwrite the file, and I don't
want to write dozens of lineinfile: statements.
Is it possible to do the equivalent of:
while read line; do
if grep "$line" /target/file >/dev/nu
I am using Ansible 1.6.6 on Solaris 10. Target system is Solaris 11 in a
VM, that is mostly idle; both in the company LAN.
I am just getting started. I don't think Solaris takes ControlPersist. I
had to make ssh_args = ""
I can't use unarchive either, it seems, as it uses the wrong tar,
I'm trying to use *template* to copy an interactive ansible playbook to the
target. I want *template* to fill in some variables before it is sent
over, but I want other variables to stay uninterpreted because they will be
filled in by *vars_prompt* when the playbook is run on the endpoint.
Michael, Stephen,
I appreciate you taking the time to respond to this old thread, and for
your thoughts, and for all your hard work on Ansible.
I will work on a PR for this.
Ned.
On Thursday, July 31, 2014 5:53:02 PM UTC-6, Michael DeHaan wrote:
>
> I'm open to making set_fact work with with_i
The PR will break some current and future things and needs some revision -
open to exploring it, but it may need to wait until after 1.7
I'm curious in particular why you needed to override the template codes
though, was the configuration file already in Jinja2 syntax, etc?
What I'm possibly sugg
I had been using custom variable enclosures with #jinja2 templates, but
since updating from ansible 1.5.4-> 1.6.x I've had these break.
I was using this feature for cases in which I wanted to provision a VM
using an ansible role that deploys a collection of support playbooks. The
idea being t
Of course:
ansible-vault edit /etc/ansible/host_vars/ansible-test
---
mysqlrootpass: XX
mysqluserpass: XX
Op vrijdag 1 augustus 2014 16:30:43 UTC+2 schreef Michael DeHaan:
>
> Can we see the host_vars file contents?
>
>
>
>
--
You received this message becau
Can we see the host_vars file contents?
On Fri, Aug 1, 2014 at 9:50 AM, Piet83 wrote:
> Thank you Michael,
>
> Only if I try both options you suggested I get i both cases:
>
> fatal: [ansible-test] => {'msg': "One or more undefined variables: 'dict'
> object has no attribute 'mysqluserpass'", '
Thanks.
Docs need to indicate when a parameter is version specific, I'll take care
of it.
On Fri, Aug 1, 2014 at 9:18 AM, Matt Martz wrote:
> The PR for using a script for the password file did include some
> documentation which is available at:
>
> http://docs.ansible.com/playbooks_vault.ht
Thank you Michael,
Only if I try both options you suggested I get i both cases:
fatal: [ansible-test] => {'msg': "One or more undefined variables: 'dict'
object has no attribute 'mysqluserpass'", 'failed': True}
fatal: [ansible-test] => {'msg': "One or more undefined variables: 'dict'
object ha
The PR for using a script for the password file did include some
documentation which is available at:
http://docs.ansible.com/playbooks_vault.html#running-a-playbook-with-vault
It is not extensive but does give some information as to what ansible
expects.
James merged the PR a few weeks ago.
On
So that's a thing already with {{ dict1 + dict2 }}?
Nice.
On Fri, Aug 1, 2014 at 8:53 AM, Brian Coca wrote:
> dict1 + dict2
>
> I also have an update to 'set theory' that will allow you to do
> dict1|union(dict2)
>
>
> --
> You received this message because you are subscribed to the Google
When using Jinja2 expressions it is not valid to use {{ }} around a
variable inside another expression.
You had:
{{ hostvars[{{target}}]['mysqluserpass'] }}
You need
{{ hostvars[target]['mysqluserpass'] }}
Which also, thankfully, is easier to read too.
Can also be written
{{ hostvars[target]
So several things I wanted to comment on.
(A) What Cap calls rollbacks aren't - it would be a rollback if it
magically understood how to undo every action. That being said, some sort
of try/except facility is intended for 1.8. "Rollback" logic is up to
you, but failing forward is a better appr
dict1 + dict2
I also have an update to 'set theory' that will allow you to do
dict1|union(dict2)
--
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-pr
Thank you both!
May I ask an other question about hostvars in templates:
When I use the follwing i a playbook everything goes well:
The variable target is provided by the --extra-vars flag on the command
line and mysqluserpass is defined in /etc/ansible/host_vars/ansible-test
and encrypted wit
Hey All,
I posted some thoughts on deploying with Ansible, specifically some
problems we tried to solve converting from Capistrano:
http://www.future500.nl/articles/2014/07/thoughts-on-deploying-with-ansible/
Michael de Haan pointed out that some of our "solutions" are deprecated for
security
I think pull requests would definitely be considered, though I'd be looking
for some folks using this module to weigh in.
Internally, we're more of a Postgres shop, so I'm a bit less the one to
comment on applicability.
On Fri, Aug 1, 2014 at 3:04 AM, Govinda Fichtner <
govinda.ficht...@goog
There's a pull request for direct GPG support in vault as well, that we
need to evaluate
https://github.com/ansible/ansible/pull/7174
"Luckily, the next major release of Ansible will include the ability for
vault_password_file to point at a script that will be run to get your
passphrase."
FYI -
We're looking at cutting 1.7 in about a week, though windows will still be
in beta status when it releases.
This doesn't mean much, just that there's no commercial support for it yet
- but also that we are also that the community around it is speeding up a
lot as referenced by some recent pull req
Am Freitag, 1. August 2014 00:45:15 UTC+2 schrieb Michael DeHaan:
>
> Please try things in 1.6.10, which is the latest version, and contains
> security updates that you will want.
>
> Per the changelog, this was fixed in 1.6.3
>
> https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
>
Thank
Hi
On Thu, Jul 31, 2014 at 03:38:07AM -0700, Filias Heidt wrote:
> Hi all,
>
> I'm getting my feet wet in ansible and I'm pretty exited so far. But I think I
> discovered a use case, which might be of interest for others:
>
> We have numerous hosts with jails on them and would like to manage th
Would it make sense to have an additional feature that completely removes
mysql slave replication from a slave with "reset slave all;" as described
here
http://www.mysqlperformanceblog.com/2013/04/17/reset-slave-vs-reset-slave-all-disconnecting-a-replication-slave-is-easier-with-mysql-5-5/
Curr
49 matches
Mail list logo
