1.4.4 is part of the last series, the latest stable release is actually
1.5.3
On Fri, Mar 21, 2014 at 1:29 PM, Eric Palmer wrote:
> I reverted back to 1.4.4 using mac ports and it works. I will wait till
> 1.6 is production. Not sure why macports is pulling a dev branch.
>
> But macports make
I reverted back to 1.4.4 using mac ports and it works. I will wait till 1.6
is production. Not sure why macports is pulling a dev branch.
But macports makes it easy to revert.
ep
On Fri, Mar 21, 2014 at 12:06 PM, Eric Palmer wrote:
> ansible --version
> ansible 1.6
>
> I did it through macpor
ansible --version
ansible 1.6
I did it through macports with
sudo port upgrade outdated
On Fri, Mar 21, 2014 at 11:56 AM, James Tanner wrote:
> facts.update(Network(module).
> populate())
>
> This was an error that made it in to the 1.5.1 and 1.5.2 releases but
> should no longer exist in 1
facts.update(Network(module).
populate())
This was an error that made it in to the 1.5.1 and 1.5.2 releases but
should no longer exist in 1.5.3 or devel. Please indicate what version of
ansible you are using and how you install it.
On Fri, Mar 21, 2014 at 11:47 AM, Matt Martz wrote:
> So, 1.6
So, 1.6 is not officially released yet. That is the 'devel' branch. Are you
running the most recent devel? I just tested here and it works.
It appears to have been fixed 10 days ago.
--
Matt Martz
m...@sivel.net
On March 21, 2014 at 10:42:02 AM, Eric Palmer (e...@ericfpalmer.com) wrote:
He
Hey all
I have a set of roles and playbooks to do some configuration on the mac
that the playbook is running on
==
the inventory file looks like
[mac]
localhost ansible_connection=local
==
the ansible.cfg file looks like
[defaults]
ask_sud