Sure here's the output. And thanks, I'll change the vars
PLAY [webservers]
*
GATHERING FACTS
***
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [ensure log direct
On Wednesday, February 12, 2014 10:37:30 PM UTC-8, Mark Maas wrote:
>
> We found we needed to mold AIX to accept a few things that should be there
> anyway:
>
> link /bin/md5sum with /bin/csum for instance. or the copy module won't work
>
We had issues with md5 but in our case it was because py
Of course I post and then realise that I missed a big one... The password
format is different between AIX and Linux. I got round this by using
jinja2 to convert the format for me...
- name: add accounts for AIX
user: name={{item.name}} append=yes createhome=yes group=group
shell={{
Yes...
I have a bunch of basic configuration tasks that I have running on Linux
and AIX. I have found a few (minor) issues so far...
1) Unpack requires gnu tar if you give it a compressed tar file, simple
solution, give it uncompressed ones. :-D
2) Python can cause issues (I've had to compil
I'm ok with the above.
On Thu, Feb 13, 2014 at 4:26 PM, Bruce Pennypacker <
bruce.pennypac...@gmail.com> wrote:
> I occasionally run into an issue with the ec2_elb module that I think
> needs to be addressed. This module is used to add and remove Amazon EC2
> instances to/from an Amazon load
Ok thanks I'll try that.
On Fri, Feb 14, 2014 at 4:49 AM, Jesse Keating wrote:
> I would edit the source code and put a debugger statement inside the if
> statement that does the print. This way when running ansible if you happen
> to get into this state, you can examine the various data, like w
I would edit the source code and put a debugger statement inside the if
statement that does the print. This way when running ansible if you
happen to get into this state, you can examine the various data, like
what it thinks the value of host_file is, and then compare that to your
filesystem.
But the file exists (and the host is there). What could I do to debug it
further?
On Fri, Feb 14, 2014 at 4:29 AM, Jesse Keating wrote:
> On 2/13/14, 12:37 PM, Ilya Ivanov wrote:
>
>> "previous known host file not found" is an Ansible message. Does anyone
>> know the conditions under which is it
I occasionally run into an issue with the ec2_elb module that I think needs
to be addressed. This module is used to add and remove Amazon EC2
instances to/from an Amazon load balancer. The API into Amazon is
asynchronous, so when you use it to add an instance to a load balancer it
issues a "i
On 2/13/14, 12:37 PM, Ilya Ivanov wrote:
"previous known host file not found" is an Ansible message. Does anyone
know the conditions under which is it triggered?
Grepping the code shows it pretty clearly:
def not_in_host_file(self, host):
host_file =
os.path.expanduser(os.path.exp
No, look closely. I just remove the arguments one by one until it succedes.
On Fri, Feb 14, 2014 at 3:44 AM, Gonzalo Servat wrote:
> You seem to be getting permission denied errors sometimes and other times
> you can login ok?
>
> Perhaps Ansible is giving the wrong error message but the underl
You seem to be getting permission denied errors sometimes and other times
you can login ok?
Perhaps Ansible is giving the wrong error message but the underlying error
is permission denied. Just taking a guess based on the output.
GS
On 14/02/2014 7:37 am, "Ilya Ivanov" wrote:
> Well, it doesn't
Well, it doesn't really matter to me whether the problem is specific or not.
Here's how a verbose ansible connection looks:
<192.168.7.188> ESTABLISH CONNECTION FOR USER: ilya
<192.168.7.188> EXEC ['ssh', '-tt', '-vvv', '-o', 'ControlMaster=auto',
'-o', 'ControlPersist=60s', '-o',
'ControlPath=/
Similar to this discussion
https://groups.google.com/d/msg/ansible-project/aBE51ToAC7A/QC3jwdPOK4MJ
I am getting this error:
failed to parse: SUDO-SUCCESS-ugbdmgqomyttgubummftugavvodrnugl
I am trying to make use of the password lookup in mysql_user like so
- name: create and/or update data
Sure, here's the output. Also, thanks I'll change the vars
PLAY [webservers]
*
GATHERING FACTS
***
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [ensure log dire
Sure, here is the output. And thanks, I'll change the vars
PLAY [webservers]
*
GATHERING FACTS
***
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [ensure log di
Cool. I cleaned it a bit and created:
https://github.com/ansible/ansible/pull/5995
Is there any guide on how to write unit tests for things like inventory
plugins? Shall I just drop a unit test in tests/?
On Thursday, February 13, 2014 4:09:51 PM UTC+2, Michael DeHaan wrote:
>
> Once you've got
Thanks for starting a discussion.
Here is how I see a feature like this.
How about if we introduce a new keyword called say "print: " similar to
debug but being an auxiliary keyword rather than the main task. So with
this you can control some extra output that comes after [changed]
[servername] =>
Maybe there could be an option to simply control the total size of each
output line.
the length-cut is simple to implement and I don't see how you could smarty
extract and show only the important information.
length=0 (default) means: I want to see everything
Le jeudi 13 février 2014 19:01:16 U
Also this wasn't posted about exit codes (shown only with -v), it was
posted about listing the item it was walking over in a loop, right?
On Thu, Feb 13, 2014 at 1:00 PM, Michael DeHaan wrote:
> I'm more curious how it would work when the item is useful and neccessary
> in some cases and no
I'm more curious how it would work when the item is useful and neccessary
in some cases and not others.
It does not feel like a global setting and it also should not be *nothing*
in the task output, or should it?
Also, trying to avoid an additional task keyword..
On Thu, Feb 13, 2014 at 12:48
Maybe just a changeable logging level will do?
Sometimes I just want to see exit code from operation, rather than a full
blown trace.
On Thursday, February 13, 2014, Michael DeHaan wrote:
> So let's not file a request, because the first thing I will ask is to have
> a discussion here. Let's tal
So let's not file a request, because the first thing I will ask is to have
a discussion here. Let's talk about what you want to do and if we can come
to something.
On Thu, Feb 13, 2014 at 12:38 PM, Rumen Telbizov wrote:
> It seems like there isn't a way to customize the output of an item (or
It seems like there isn't a way to customize the output of an item (or
otherwise any task).
Would anybody else be interested in having this feature? I could file a
request/ticket with a suggestion.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" gro
Once you've got it tweaked, it can live here:
https://github.com/ansible/ansible/tree/devel/plugins/inventory
On Thu, Feb 13, 2014 at 9:06 AM, Michael DeHaan wrote:
> I'd be fine to include something like this in examples for those that want
> to use it.
>
> Pull request would need a few thi
I'd be fine to include something like this in examples for those that want
to use it.
Pull request would need a few things:
So the DOCUMENTATION string in here makes it look like it's a module, but
it's really an inventory script, so I'd remove the "DOCUMENTATION" YAML
block, since that was a bit
Hello,
at first, thanks for all the good work on Ansible, I like the project a
lot! I spent more than a year working with Puppet, and I have to say that
using Ansible is much less headache.
I tend to work with nodes of various nature. Some inventory info I can get
from remote service (OpenStac
Hi,
The yum_repository module sounds exactly what I've been looking for.
Unfortunately the url doesn't work and I'm unable to find it anywhere. Is
it still available somewhere?
Thanks in advance,
/Johan
Den söndagen den 16:e juni 2013 kl. 19:56:59 UTC+2 skrev Matt S:
>
> I just happen to have
Thanks for clarification. And - of course - thanks for working 25 hours a
day on this great product and answering community questions!
Oliver
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receivin
I meant the workaround details at the bottom of the issue description
You're right though, it was #4807 that never amounted to much. Mainly because I
couldn't get the fix right and wasn't motivated enough to need to get the fix
right!
Will
On 13 Feb 2014, at 23:41, Michael DeHaan wrote:
> Hi
Hi Will,
I'm confused a bit about what you are referring to in the ticket.
As I recall we got the async math bugfix completed in the end.Is there
a chance you linked a different ticket by mistake possibly?
On Wed, Feb 12, 2014 at 6:48 PM, Will Thames wrote:
> This came up for me in the
Can I see the output so I can see the error at the point it occurs?
BTW, quick note -- I should point out that you are still using $old
variables
Variables should be using the Jinja2 style as denoted on docs.ansible.com,
i.e. {{ variable }}
In 1.4.X, these emit deprecation warnings, and they wil
Merged in and now available on the devel branch, thanks!
On Thu, Feb 13, 2014 at 8:31 AM, Brian Coca wrote:
> I was fixing it for a BSD corner case so I went ahead and added a 2nd path
> for AIX
>
> https://github.com/ansible/ansible/pull/5993
>
> --
> You received this message because you are
I was fixing it for a BSD corner case so I went ahead and added a 2nd path
for AIX
https://github.com/ansible/ansible/pull/5993
--
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,
The md5sum logic is a bit "fancy". BTW, it's been suggested that we can
have a setup module fact that returns the md5'r to use, and if set, bypass
this logic for future calls.
I don't think it really saves a lot, but would make -vvv output at least
cleaner.
On Thu, Feb 13, 2014 at 8:06 AM, Bri
It was deleted because it was considered flamebait and was based on some
invalid assumptions, and Chris and I have since discussed and are in a
happy place.
I had initially replied because it was an open letter to the list, without
realizing that it didn't make it to the list, and there was no sin
hmm, seems someone added with an alternative path:
"(/usr/bin/csum -h MD5 %s 2>/dev/null)" % path # AIX
--
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 an
On Thu, Feb 13, 2014 at 1:37 AM, Mark Maas wrote:
> /bin/csum
This would be easy to add to the current remote_md5 function. Just one
question, how does csum act when the target is a directory?
--
Brian Coca
Stultorum infinitus est numerus
011101110010011001010110111000100111011101100
I can release version 3000 tomorrow.
Just have to edit the VERSION file and hit "make" :)
On Thu, Feb 13, 2014 at 1:36 AM, Walid wrote:
> I will use development until 2.x release is out
>
>
> On 13 February 2014 07:03, Brian Coca wrote:
>
>> soo ... when is 1.6 being released?
>>
>> :-p
>>
I've been looking at all that, but work gets in the way! :)
Right now I'm going to ignore that error in the lone box and get some
things done. When I'm finished with the whole reorganisation, the issue
most probably will have gone away...
anyway, thanks for the help! appreciated!
On Thursday, 13
no but system root or what ever user you are running ansible as (su, sudo,
user) could have different permissions on an NFS mount than system
permissions. root could be squashed, ids could be not mapped correctly
On 13 February 2014 12:48, Makimoto Marakatti wrote:
> yes, /home is on nfs on som
yes, /home is on nfs on some systems, but even if that raises chances of
issues with ansible, it's not conclusive. Some of the hosts that indeed
have the /home shared do not show any issues. So there's something going
on, but haven't yet figured it out.
On Thursday, 13 February 2014 09:06:06 UT
I got the daily mailing list digest and wanted to read the the initial
posting and Michael DeHaans reply. But Google groups tells me "The
requested topic cannot be found. It might have been deleted."
As Michael DeHaan did answer in the first place I guess it was not so
offensive that censorship
is any of the /tmp and $HOME/tmp in a shared file system?
On 13 February 2014 11:34, Makimoto Marakatti wrote:
> No difference there really. I even tried to chmod 777 ~/.ansible to see if
> it made a difference, but no luck.
> I will get to the root cause eventually... :)
>
>
> On Wednesday, 12
No difference there really. I even tried to chmod 777 ~/.ansible to see if
it made a difference, but no luck.
I will get to the root cause eventually... :)
On Wednesday, 12 February 2014 16:16:07 UTC, Walid Shaari wrote:
>
> what are the /tmp and $HOME/tmp permissions? I am wondering if it is a
45 matches
Mail list logo
