Likewise, the 'end_role' is a much requested feature to help simplify role
logic.
https://github.com/ansible/ansible/issues/22286
On Tue, 10 Oct 2023, 11:01 Dick Visser, wrote:
> Hii
>
> There is the 'end_play' meta task that will end the current play.
> We use playbooks that have several
On Wed, 12 Jul 2017, Rod Oliver wrote:
Sorry about the late response. I was wondering how well used they are, how
stable and reliable the modules are considered to be. The background is
that my organisation is looking for a solution to migrate ACI provisioning
and I'd like to advocate Ansible
Hi,
So one of the problems we want to tackle with Ansible Sprints is to
bring down the number of open issues and open PRs. The idea of doing
Sprints that have a strong focus on advancing and closing issues/PRs is
something we have been thinking about for some time.
Now is the time to see
On Sun, 25 Jun 2017, David Baumann wrote:
Yeah i know that is based on http.sys
I checked also the http/https binding over netsh and compare them between a
working and non working system. Realy no clue why this happening.
I put now 3 Days of work into that debugging, now i switch to ensure
On Fri, 23 Jun 2017, Reiner Nippes wrote:
I'm starting two ec2 SLES12 instances with ansible. After they are
up the same playbook should configure the machines.
So I inculde
- name: Wait for connection to
wait_for_connection:
after the ec2: module. Ansible is waiting for connecting some
On Thu, 22 Jun 2017, Rod Oliver wrote:
Hi All,
I'm aware of modules for ACI on Github
(https://github.com/jedelman8/aci-ansible), however they haven't seen a lot
of updates in the last while. Is anyone using them who might be prepared to
chat about their experiences?
Sure, I happen to know a
On Tue, 9 May 2017, Josh Smift wrote:
JBS> https://docs.ansible.com/ansible/template_module.html doesn't say
JBS> that you can specify a directory as the value of the dest parameter.
JBS> Should that work?
JBS>
JBS> If it should work to specify a directory, should 'diff' work as well?
JBS>
JBS>
On Tue, 9 May 2017, Josh Smift wrote:
If you use the template module and the dest parameter specifies a
directory, the module creates a file in the directory with the same name
as the value of the src parameter. However, if you then change the source
contents, and run ansible-playbook with
On Sat, 1 Apr 2017, Uditha Desilva wrote:
Even in RHEL 7, the version of pexpect isn't good enough. The easiest option is
to use pip to install it from PyPi.
My solution to expect is documented in the shell-module documentation:
http://docs.ansible.com/ansible/shell_module.html
Which
On Wed, 19 Apr 2017, 'J Hawkesworth' via Ansible Project wrote:
I would recommend using win_package - that's what I use to maintain java
versions in our playbooks.
For info, recent java versions like to upgrade themselves. While this is
laudable it may cause unexpected behaviours as clusters
On Wed, 19 Apr 2017, Jordan Borean wrote:
There were plans to deprecate win_msi in the 2.3 release in favour of
win_package but win_package was never hardened as a core module so it never
became official. That being said win_package is the recommended of the 2 but
there have been a few cases
On Tue, 9 May 2017, Trond Hindenes wrote:
Hope someone can help me shed some light on this one:
Since Ansible is python-based, us Windows dudes generally have to stick an
extra backslash anywhere we're manipulating Windows paths. However, in some
cases this causes unexpected behavior. In my
On Fri, 2 Dec 2016, fabrice.pe...@socrambanque.fr wrote:
I have just discovered that the *win_file* module does not support
*check_mode*.
Is it a regression?
If not, are there any developments in progress for this module to support
check mode?
We are working hard to improve the Windows
On Tue, 14 Feb 2017, Hmdi Bz wrote:
when I execute :
$ ansible windowsTest -i inv.ini -m win_ping
I get this error:
192.168.1.2 |Unreachable! => {
"changed": false,
"msg": "basic: the specified credentials were rejected by the server",
"unreachable": true
}
Could you run this with
On Tue, 14 Feb 2017, rong zhao wrote:
My remote hosts' management port is serial console over LAN.
When connect by ssh manually, I use ops account connect to remote hosts,
and then it become the Linux console, I just run ssh command.
Now, I use ansible -m ping to test reachable, it
On Tue, 14 Feb 2017, Mario S. wrote:
New to Ansible here...
I can't seem to make multiple values work for the remoteip variable.
For instance, I want to allow multiple IP subnets to work through a
firewall rule.
And also noticed the ICMPv4 protocol isn't supported properly.
Please advise,
On Sun, 8 Jan 2017, Andy Mangion wrote:
Thanks sir; that makes sense. It appears my question was more due to my
limited experience in selinux rather than poor documentation so I wouldn't
suggest a change in documentation for now.
Well, the documentation is there also for users with limited
On Wed, 4 Jan 2017, Danny Rehelis wrote:
Anyone? :-(
Never tried it myself, but wouldn't this work ?
- include: update-windows.yml
until:
retries: 10
You will have to make sure that the condition is based on facts from the
tasks in your taskbook, which include win_updates and
On Thu, 5 Jan 2017, Mick st john wrote:
ANSIBLE VERSION USED: 2.2.0
I am trying to deploy a virtual machine from a template that is already
present on an ESX which is managed by a VCenter Server.
I'm getting the following error after the execution of my playbook:
"Cannot connect to x.x.x.x:
On Wed, 4 Jan 2017, Andy Mangion wrote:
I am using Ansible 2.2 and wanted to implement a step to set a selinux
context of a file using the sefcontext module. After some work to get it to
work on RHEL 7; it is successfully writing to the local policy file the new
rules I defined however the
On Tue, 2 Feb 2016, Tuomas-Matti Soikkeli wrote:
I believe it's because zip doesn't support it like tar does. So I suppose
there is no fix for that other than manually comparing the contents with
python ZipFile api. Unfortunately zip lacks most of the unixy features
which tar provides like
Hi,
I wrote a new stdout callback plugin, named "dense", with the aim to make
the output more compact and readable, while valuing screen-estate .
During a playbook-run progress is updated using terminal capabilities.
Successful tasks disappear from screen, but if changes or errors occur,
On Thu, 25 Feb 2016, Mike Biancaniello wrote:
I have done similar things to enable my plugins for v1 AND v2. Essentially:
from ansible import __version__ as ANSIBLE_VERSION
if ANSIBLE_VERSION.startswith('2'):
else:
More recently, I am encouraging everyone to upgrade to v2 and trying to
be identical (we could
have done something similar for other v1 functions, but prefered to
stick as closely to v2 as possible, and consider v1 the exception as
much as possible.
Below is the hybrid filetree plugin. Feedback is much appreciated:
# (c) 2016 Dag Wieers &l
On Wed, 24 Feb 2016, Brian Coca wrote:
It is 'on the list' to document it, but we also have many other things on
that list that are much higher priority: documenting other plugins,
migration path to 2.0, making plugins work under 1.9 AND 2.0, document
testing, and in general bugfixes and
On Fri, 19 Feb 2016, Austin Butler wrote:
The lineinfile module is consistently reporting changed on a step. The
actual replace works fine the first time, and it's not harming anything on
subsequent runs so I guess it's mostly a cosmetic issue, but still I am
trying to keep changes to, you
Hi,
At $customer we have a tree of files that need to be distributed, and most
of these files actually require to be templated to the target systems.
The playbook is quite complicated as with_fileglob is carefully written to
do the correct actions on the various files, however since this
On Tue, 24 Mar 2015, Vince Skahan wrote:
On Tuesday, March 24, 2015 at 6:46:27 AM UTC-7, Jonathan Davila wrote:
You could try to variablize the values of the module parameters into
os-specific vars files and then do conditional include statements based on
the os.
Where you would have files
On Thu, 5 Mar 2015, Craig White wrote:
Seems that the 'script' module wants a local file but I need the local file
to be a template with variables ./templates/my_script.sh
# Run script which removes the directory
- name: perform OpenLDAP setup and clean up
script: /tmp/slapd/add_ldifs.sh
On Fri, 6 Mar 2015, Serge van Ginderachter wrote:
On 6 March 2015 at 18:47, Craig White white.n...@gmail.com wrote:
given that I am a newbie, my opinions lack perspective. I think the
'script' command should be able to be gathered from a template because
ansible is just a glorified shell
On Thu, 5 Mar 2015, Jim McMahon wrote:
Is there a way to set a variable just for a task? Say the task uses the
template module and I want to set a variable just for that task that is not
specific to the host I'm on.
You can define a variable (conditionally) inside the template, or use
On Thu, 26 Feb 2015, Tiglath wrote:
I have used Ansible for our data center migration and now it's time to tell
the whole department about it.
The problem is that I did not need to make very advanced use of Ansible to
automate the big move, and covering it will be rather short and boring.
I
On Sun, 18 Jan 2015, Peter Mooshammer wrote:
On Sunday, January 18, 2015 at 4:57:39 PM UTC-8, James Martin wrote:
Have you looked into using the GCE dynamic inventory?
http://docs.ansible.com/guide_gce.html#gce-dynamic-inventory
I wanted to write a play that sets up and provisions a node
On Tue, 11 Nov 2014, Azul Inho wrote:
just a heads up,
I run RH6.5, not able to upgrade at the moment to 6.6 (and it looks like it
wouldn't help either), I have worked around the ControlPersist issue by
installing a openssh6 client on my control host box (/opt/openssh6),
I then have a wrapper
Hi,
As some of you may know, Red Hat backported the ControlPersist
functionality to the OpenSSH version that ships with RHEL6.
This is terrific since RHEL users can now use this technique to speed up
Ansible.
However, after some testing it seems to fail for the very first
connection. What
Hi,
Is it normal for group_by to take 4 minutes to evaluate 2800 servers ?
We often start off with a group_by to simplify the playbook (and not
overdesign our inventory script) and have noticed that with a large number
of systems it doesn't scale very well.
--
Dag
--
You received this
On Thu, 9 Oct 2014, Michael DeHaan wrote:
Starter question: ansible --version
It was version 1.6.3, but meanwhile it seems that 1.7.2 has this fixed
although I haven't confirmed it for every use-case in production. Will
check on Monday.
--
Dag
--
You received this message because you
=22 state=stopped
timeout=360
- name: Waiting for system(s) to come back up
local_action: wait_for host={{ansible_ssh_host}} port=22 state=started
timeout=900
- name: Testing whether system is working fine
action: ping
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com
).
Another option is to extend the uri module with an option like:
content_as_json=yes
My prefered solution is to include this in the inventory step (outside of
Ansible) so that it can be processed asynchronous (and cached) to Ansible.
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com
}}
when: user_data is defined
Right, didn't think of doing it like this. Quite powerful indeed.
Thanks :)
--
-- dag wieers, d...@wieers.com, http
know I am not going to change your mind, but I care too much to not even
try to make the case (that you seem to ignoring).
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact
On Tue, 4 Mar 2014, Michael DeHaan wrote:
On Tue, Mar 4, 2014 at 8:03 AM, Dag Wieers d...@wieers.com wrote:
On Tue, 4 Mar 2014, Michael DeHaan wrote:
I'll recap for the purposes of the list:
The question is removal of an undocumented and unclear flag, that modelled
what was a Tri-state
and support's concern.
That said, I would definitely fix the logic that validates from
SETUP_CACHE whether setup was already run, and make a special boolean or
fact to keep track of whether it has run. Which IMO is the real bug that
needs fixing.
--
-- dag wieers, d...@wieers.com, http
what confused me here is that this is
piggy-backed by the facts-gathering logic, rather than part of the setup
module as I was used to.
So in my opinion, a call to setup (through an action) should expose this
as well. My bad :)
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit
On Tue, 4 Mar 2014, Dag Wieers wrote:
On Tue, 4 Mar 2014, Brian Coca wrote:
Is it not what module_setup: true, was for?
Now I feel stupid :)
https://github.com/ansible/ansible/commit/fedfd187749654105a22be20c27e0050bc722d0a
But yes, that's the logic we (I guess) copied however I didn't
not setting gather_facts in each of your plays?
We noticed the same thing. Facts are gathered for every play, rather than
once per playbook.
The playbook does not mention gather_facts, nor did we specify anything in
/etc/ansible/ansible.cfg related to facts gathering.
--
-- dag wieers, d
On Mon, 3 Mar 2014, Dag Wieers wrote:
On Mon, 3 Mar 2014, James Tanner wrote:
On 03/01/2014 09:16 PM, Dustin C. Hatch wrote:
On 02/28/2014 02:56 PM, Michael DeHaan wrote:
Or should we say, it escapes!
And it's on PyPi now.
http://blog.ansibleworks.com/2014/02/28/ansible
, and if it was, the silent majority
has already spoken ! ;-)
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you are subscribed to the Google
stuff like this in the future (as it seems
that's what this is about mostly) let me know what phrases you like me to
use for sugarcoating. A template will do just fine ;-)
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any
to even
bother sending anything upstream as long as this is considered a best
practice.
PS Maybe you ought to set up your own bugzilla and disable the Github
issue-tracker altogether, rather than going down this path...
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux
-requests ?
Besides, have you looked with the Github people to see whether they could
add a custom (template) text to the issue input form ?
Seems to me that is what you (and pretty much every other project) needs,
rather than have a bot comment on opened issues after the fact...
--
-- dag
.
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you are subscribed to the Google Groups Ansible
Project group.
To unsubscribe
(!).
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you are subscribed to the Google Groups Ansible
Project group
not for a system that gives access to our complete
datacenter ;-))
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, cont...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you
54 matches
Mail list logo
