[ansible-project] Ansible-4.6.0 release

Hi all, We're happy to announce that the ansible-4.6.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible-4.5.0 has been released

Hi all, We're happy to announce that the ansible-4.5.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible-4.4.0 released

Hi all, We're happy to announce that the ansible-4.4.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible-4.3.0 has been released

Hi all, We're happy to announce that the ansible-4.3.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible 4.2.0 released

Hi all, We're happy to announce that the ansible-4.2.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible-4.1.0 release

Hi all, We're happy to announce that the ansible-4.1.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need

[ansible-project] Ansible 4.0.0 final has been released!

- A unified porting guide for collections which have opted-in is available here: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubs

[ansible-project] Ansible-3.4.0 released

Hi all, We're happy to announce that the ansible-3.4.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the

[ansible-project] Ansible-4.0.0rc1

Hi all, We're happy to announce that the Ansible-4.0.0 release candidate 1 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible 3 package (Ansible 3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in

[ansible-project] Ansible-4.0.0 beta2 released

Hi all, We're happy to announce that the Ansible-4.0.0 beta2 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core

[ansible-project] FYI: Reminder about ansible 3 & 4 release dates

Just a brief reminder about the Ansible 3 and 4 schedule: * The last Ansible 3 release is planned for May 11, 2021 * Ansible 4.0.0 release candidate 1 is also planned for May 11, 2021 * If there are no blocker bugs discovered, Ansible 4.0.0 final will be made on May 18, 2021 -Toshio -- You

[ansible-project] Ansible 4.0.0 beta1 release

Hi all, We're happy to announce that the Ansible-4.0.0 beta1 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core

[ansible-project] Ansible3.3.0

Hi all, We're happy to announce that the ansible-3.3.0 package was released on April 20! The update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the

[ansible-project] Ansible-3.2.0 released

Hi all, We're happy to announce that the ansible-3.2.0 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the

[ansible-project] Ansible-3.1.0 release and ansible-4.0 alpha1 delay

Hi all, We're happy to announce that the ansible-3.1.0 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the

[ansible-project] Ansible-3.0.0 released

Hi all, We're happy to announce that the ansible-3.0.0 package is now available! This update is based on the ansible-base-2.10.x package just like ansible-2.10 was so the changes shouldn't be too major. However, it does contain new major versions of many collections which means that there will be

[ansible-project] Re: Ansible-3.0.0 release candidate 1

at yesterday's Community IRC meeting we voted to allow a slip to Thursday, February, 18th if we needed it. I just didn't want anyone to be surprised if Ansible-3.0.0 shows up a few days late! Thanks, -Toshio On Tue, Feb 9, 2021 at 3:59 PM Toshio Kuratomi wrote: > > Hi all, > >

[ansible-project] Ansible-3.0.0 release candidate 1

/porting_guide_3.rst Thanks for testing! -Toshio Kuratomi -- 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...@google

[ansible-project] Re: Ansible-2.10.7 released.

Small correction. The pip install instructions should read: $ pip uninstall ansible $ pip install ansible==2.10.7 --user Thanks! -Toshio On Tue, Feb 9, 2021 at 1:28 PM Toshio Kuratomi wrote: > > Hi all, > > We're happy to announce that the ansible-2.10.7 package is now

[ansible-project] Ansible-2.10.7 released.

Hi all, We're happy to announce that the ansible-2.10.7 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. Ansible-2.10.x is a big change in how the Ansible package is built so if you missed out on all the changes that

[ansible-project] Ansible-3.0.0 beta1 released

Hi all, We're happy to announce that the ansible-3.0.0 beta1 package is now available! This update is based on the ansible-base-2.10.x package just like ansible-2.10 was so the changes shouldn't be too major. However, it does contain new major versions of many collections which means that there

[ansible-project] Ansible-2.10.6 has been released

Hi all, We're happy to announce that the ansible-2.10.6 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. Ansible-2.10.x is a big change in how the Ansible package is built so if you missed out on all the changes that

[ansible-project] Ansible-2.10.3 released: quick fix for installation issue

/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- 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.co

[ansible-project] Re: Ansible-2.10.2 has been released

at 4:42 PM Toshio Kuratomi wrote: > > Hi all- > > We're happy to announce that the ansible-2.10.2 package is now > available! This update contains bugfixes and new, backwards > compatible features in the contained collections as well as bringing > in ansible-base-2.10.3 as a de

[ansible-project] Ansible-2.10.2 has been released

/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- 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.co

[ansible-project] Ansible-2.10.1 has been released

of discussion. Porting Help - There's a unified porting guide for collections which have opted-in. You can find that at: https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- You received this message because

Re: [ansible-project] Ansible-2.10.0 has been released!

a problem with as pypi is generally the go to location for python packages anyway but I can't remember what the reasoning was. Thanks for checking on that! -Toshio On Wed, Sep 23, 2020, 1:35 AM Michael Ströder wrote: > On 9/23/20 1:22 AM, Toshio Kuratomi wrote: > > The tar.gz of the re

[ansible-project] Ansible-2.10.0 has been released!

ting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- 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...@g

[ansible-project] Ansible-2.10.0 release candidate 1

l is closest and the Community Team will always move it if needed. Thanks! -Toshio Kuratomi -- 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 ansi

[ansible-project] Re: Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

/answer/registration I highly recommend registering and testing that you are able to participate in #ansible-community discussions before the meeting on the 17th! -Toshio On Thu, Sep 10, 2020 at 8:29 AM Toshio Kuratomi wrote: > > Howdy folks! > > We're entering the final weeks of the An

[ansible-project] Re: Ansible 2.10.0 beta 1

Toshio Kuratomi wrote: > > Hi all- > > For all those wanting to test the next version of Ansible, we're happy > to announce that Ansible 2.10.0 beta1 is now available on PyPI! > > Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2) > package via a depende

[ansible-project] Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

that wasn't noticed previously in the Ansible-2.10.1 release. So please test out the beta and release candidate now and report candidate blockers before the meeting. Thank you, Toshio Kuratomi On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi wrote: > > Hi all- > > For all those wanting to t

[ansible-project] Ansible-2.10.0 beta2

you aren't sure where your bug falls, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group

[ansible-project] Changes to the ansible-2.10.0 pre-release schedule

://raw.githubusercontent.com/ansible/community/master/meetings/ical/community.ics * 22-Sep-2020: If no blockers are found, ansible-2.10.0 final will release as previously scheduled. Thanks for understanding! -Toshio Kuratomi -- You received this message because you are subscribed to the Google

[ansible-project] Ansible 2.10.0 beta 1

will always move it if needed Thanks! -Toshio Kuratomi -- 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

[ansible-project] Minor change to the license listed in the project's README to GPLv3+

Greetings all, I'm just letting you all know that I'm merging this PR today: https://github.com/ansible/ansible/pull/65124 It changes the license listed in the README from "GNU General Public License v3.0" to "GNU General Public License v3.0 or later". We consider this a clarification rather

[ansible-project] New Ansible release 2.9.0

, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google

[ansible-project] New Ansible releases 2.8.6, 2.7.14, 2.6.20, and 2.9.0rc4

or if any of your working playbooks break when you upgrade to 2.8.6, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You

[ansible-project] New Ansible pre-release 2.9.0rc1

the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups

[ansible-project] New Ansible release 2.8.5

/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails fro

[ansible-project] New Ansible releases 2.8.4, 2.7.13, and 2.6.19

/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails fro

[ansible-project] New Ansible release 2.8.3

In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails fro

[ansible-project] Re: New Ansible releases 2.8.2, 2.7.12, and 2.6.18

One additional note: The Deb builds for the Ansible PPA failed. We're working on getting those built and uploaded but no ETA yet. (Tomorrow is a US holiday so it cuts into the time available to diagnose, fix, and then release those). -Toshoi On Wed, Jul 3, 2019 at 1:56 PM Toshio Kuratomi wrote

[ansible-project] New Ansible releases 2.8.2, 2.7.12, and 2.6.18

and the one that doesn't. Thanks! -Toshio Kuratomi -- 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.co

[ansible-project] New Ansible releases 2.8.1

In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails fro

[ansible-project] New Ansible releases 2.7.11 and 2.6.17

, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed

[ansible-project] New Ansible release 2.8.0

: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubs

[ansible-project] New Ansible release 2.7.10 and 2.6.16

or if any of your working playbooks break when you upgrade to 2.7.10, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi

[ansible-project] Ansible 2.7.9 and 2.6.15

regressions from playbooks which work on 2.7.8 and prior, please open a GitHub issue, and be sure to mention you're using 2.7.9. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this grou

[ansible-project] Ansible 2.7.8, 2.6.14, and 2.5.15

! -Toshio Kuratomi -- 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, send email

[ansible-project] Dropping Fedora rpms from https://releases.ansible.com/

Hey all, Recently we had a discussion internally about whether to build upstream Ansible rpms on Fedora 29 using Python3 or Python2. This lead to a question about how useful the Fedora rpms Ansible releases on https://releases.ansible.com/ are. We found that for each of the Fedora releases, the

[ansible-project]

/ansible/devel/porting_guides/porting_guide_2.7.html to help migrate your content to 2.7. If you discover any errors, or if you see any regressions from playbooks which work on 2.7.6 and prior, please open a GitHub issue, and be sure to mention you're using 2.7.7. Thanks! -Toshio Kuratomi -- You

[ansible-project] Ansible 2.7.6 and 2.6.12

regressions from playbooks which work on early releases, please open a Github issue, and be sure to mention which Ansible release you're using. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubs

[ansible-project] Ansible 2.5.14, 2.6.11, and 2.7.5 are available

Changelog: https://github.com/ansible/ansible/blob/v2.5.14/changelogs/CHANGELOG-v2.5.rst SHA256: 695ac8ebce0be57062924ff90f4b98cd61caa99cd21cdb10a964e3320524a069 ansible-2.5.14.tar.gz -Toshio Kuratomi (@abadger1999) -- You received this message because you are subscribed to the Google Groups

Re: [ansible-project] [WARNING]: The src option requires state to be 'link' or 'hard'. This will become an error in Ansible 2.10

>From the name of your task, it looks like you mean to use copy:, not file: -Toshio On Mon, Nov 26, 2018, 6:19 PM Ronnie10 Hi All, > > I have the following ansible codes, however when I run molecule test, it > gave me the error as my subject, anyway to fix that? > > - name: Copy file to config

[ansible-project] Ansible-2.7.2

.html to help migrate your content to 2.7. If you discover any errors, or if you see any regressions from playbooks which work on 2.6.x and prior, please open a Github issue, and be sure to mention you're using 2.7.2. Thanks! -Toshio Kuratomi -- You received this message because you

Re: [ansible-project] How to reopen issue in ansible (github)

Open a new issue. If you think it is related to the old issue, link to the old issue in the new one. Since that issue says that the issue was fixed, testing with the version containing the fix could tell us if there was a regression versus a new and unrelated problem. On Wed, Nov 7, 2018, 4:29

[ansible-project] Ansible-2.7.1 is released

you're using 2.7.1. Thanks! -Toshio Kuratomi (abadger1999) -- 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...@google

Re: [ansible-project] Ansible 2.7 yum module issues

Are you able to grab the yum module from the stable-2. 7 bench to give it a try? There were a couple fixes to it after 2.7.0 and are merged for 2.7.1. i know at least one had to do with config files but i don't recall the symptoms so i can't be sure it's the same thing.

Re: [ansible-project] Re: how to use an pipe like < < in ansible ?

Without an error message I'm not sure whether I'm looking at the same thing but this looks like a portability problem with the shell script you are attempting to use. In /bin/sh (implemented by bash), I get the following error: $ /bin/sh *[stable-2.7]

[ansible-project] 2.7.0 Final has been released!

. Thanks! Toshio Kuratomi (@abadger) Ansible Core Engineering / 2.7 release manager -- 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-projec

Re: [ansible-project] unicode, json...

It appears that nlb contains a string. Perhaps because of the initial space in ``` nlb: " {{ nlb.stdout |from_json }}" ``` ? On Fri, Aug 31, 2018 at 10:12 PM, Karl Auer wrote: > I have an AWS CLI command that returns this (I've truncated it): > > changed: [localhost] => {"changed": true,

Re: [ansible-project] Re: issue with ansible dry-run mode (--check) on package installation tasks (yum and apt modules)

The yum task succeeded. It's the subsequent fail that is failing. You can make any other module +fail react in the same way: - file: path=/var/tmp/i_do_not_exist_yet state=directory - stat: path: /var/tmp/i_do_not_exist_yet register: file - fail: msg: "File

Re: [ansible-project] ansible replace with_items prepends the letter 'u'

Is it showing up in your sshd_config file or just in the display of what each item was? -Toshio On Fri, May 4, 2018, 8:55 AM wrote: > I'm trying to use the replace module to update SSL ciphers and seem to be > running into a Unicode issue. > > The code: > > --- > -

Re: [ansible-project] Ansible custom module_utils in Ansible 2.1 & 2.2

On Tue, Apr 17, 2018, 11:35 PM Raja Shekar wrote: > > Hi, > > I am working on Juniper.junos role. We are trying to correct our module_utils > import style to include ansiballz framework. Currently, for our role we > support Ansible >= 2.1. I understand that there was no

[ansible-project] Subject: Ansible 2.4.4.0 Final released

Hi all, For everyone who has not yet decided to upgrade to ansible-2.5.0 we're happy to announce that ansible- 2.4.4.0 has been released. -- How do you get it? The tar.gz of the release can be found here:

[ansible-project] Ansible 2.4.4 RC2 is ready for testing

bugs are discovered. Non-critical bugfixes will be released in the 2.5.x or newer release serieses.) Thanks for testing! Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop

Re: [ansible-project] Error while running bigip_node module

Setting ansible_python_interpreter=/path/to/python2.7 should do it for you unless the scl python2.7 doesn't know where its own libraries are (haven't used scl python so I don't know the answer to that off the top of my head) You can set that on the command line using the --extra-vars option to

Re: [ansible-project] Re: Permission denied while copy with sudo (Related to issue 2837)

Your having a different problem than the person you replied to. Your issue is that you don't have permission on the directory that you are asking ansible to create (/etc/ ). The original poster was having problems with an internal ansible temporary directory. For your issue, you need the

Re: [ansible-project] Re: Permission denied while copy with sudo (Related to issue 2837)

There's a configuration option, remote_tmp. Setting that to a system directory (like /tmp or /var/tmp ) can fix this error. On Mar 8, 2018 5:04 PM, "Vamsi krishna" wrote: > Hi vincent, > > mee to facing the same issue... > changing the tmp directory means, what you

Re: [ansible-project] Re: /tmp/.ansible/tmp not write-able by all users

If you specify /tmp/.ansible/tmp as the remote_tmp, then you become responsible for ensuring that the correct users have permission to read, write, and search that directory. Ansible deals with permissions below that directory only. There was a bug in the 2.5 branch (I believe fixed in the

[ansible-project] Ansible 2.4.4 RC1 is ready for testing

. -- I'm aiming to have 2.4.4 final come out the week after 2.5.0 final is out. So do test this out if you're intending to stay on 2.4.x a while longer but note that the final of 2.4.4 won't be released until after 2.5.0. Thanks! Toshio Kuratomi -- You

[ansible-project] Release schedule for 2.4.4 and beyond

Greetings all, I just wanted to say a brief word about my intention as the 2.4.x Ansible Release Manager forgetting 2.4.4 out the door and any further 2.4.x releases after that. Release Schedule for 2.4.4 == My plan is for 2.4.4 to be released shortly after 2.5.0 final

Re: [ansible-project] Can Ansible consider switching from Google Groups to a Discourse instance?

I don't think this would happen. I have asked the core team about switching from Google groups to a mailman 3 instance that has a forum-like interface to the archives but there didn't seem to be any other interest in that. -Toshio On Feb 18, 2018 12:34 PM, "David Reagan"

[ansible-project] Ansible 2.4.3 has been released

On behalf of the entire Ansible open source community, we are very happy to announce that Ansible 2.4.3 has been released! This release includes many bugfixes to the 2.4 codebase. For full details, please see the Changelog: https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md As

[ansible-project] Ansible-2.4.3-rc3

hoping that this will be the last release candidate before 2.4.3.0 final. Thanks! Toshio Kuratomi -- 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 ansib

[ansible-project] Ansible 2.4.3.0 rc2 ready for testing

. -- The notable changes in this rc are some improvements for speed and memory when using include_role and some butg fixes for the azure modules. If all goes well with testing of this, we should be releasing 2.4.3.0 final next week! Thanks, Toshio

[ansible-project] Ansible 2.4.3 RC1 is ready for testing

your own .tar.gz (output will be dist/ansible-2.4.3.0.tar.gz): $ make sdist If you discover any errors, or if you see any regressions from playbooks which work on 2.4.2 and prior, please open a Github issue and be sure to mention you're testing against this release candidate. Thanks! Toshio

Re: [ansible-project] In an Ansible task, what is the proper way to run a script in the background?

Or option three: use async:. http://docs.ansible.com/ansible/latest/playbooks_async.html If the script is something you want to run and exit after performing its tall, I think async is the most idiomatic. If the script is more like a daemon, having nohup in the script feels right to me but I

Re: [ansible-project] absolute import error for centos 5 environment

You need a newer version of python or an older version of ansible. Ansible-2.3 was the last release series to support python-2.4 on the managed machines (it still required python-2.6 or greater on the controller but you could manage machines with only python 2.4 installed ). -Toshio On Dec 20,

Re: [ansible-project] Trying to duplicate a Bash script into ansible -- Not sure how to best handle alternatives with Slaves

If you don't need idempotence (I assume you don't since the shell module doesn't have idempotence either) I'd use the script module with your existing bash script. -toshio On Dec 13, 2017 7:39 AM, "Justin Seiser" wrote: > I see there was a feature >

Re: [ansible-project] How to configure audible not to use MD5?

ot;validate": null } }, "md5sum": null, "mode": "0664", "owner": "badger", "secontext": "unconfined_u:object_r:user_home_t:s0", "size": 5664, "src": "/home/badger

Re: [ansible-project] How to configure audible not to use MD5?

> previous FIPS forbidden algorithm error ignored\n > > Thanks, > -Veena > > On Tuesday, December 5, 2017 at 8:59:12 PM UTC+5:30, Toshio Kuratomi wrote: >> >> Template and copy will work just fine in FIPS mode. The md5 return >> value will just be empty. Try it

Re: [ansible-project] How to configure audible not to use MD5?

t there is no alternative for > "template". The use case is to run ansible tasks with FIPS enabled mode. > > > On Tuesday, December 5, 2017 at 8:52:06 PM UTC+5:30, Toshio Kuratomi wrote: >> >> Just confirmed that template uses the copy module under the cov

Re: [ansible-project] How to configure audible not to use MD5?

Just confirmed that template uses the copy module under the covers. That means if md5 is disabled on the remote machine, then it will not return an md5 hash. -Toshio On Tue, Dec 5, 2017 at 6:38 AM, Toshio Kuratomi <tkura...@redhat.com> wrote: > I'll check that template uses the s

Re: [ansible-project] How to configure audible not to use MD5?

I'll check that template uses the same rules as the copy and start modules not in general if md5 is disallowed on a not do (for instance, fips mode), the module simply won't return an md5 hash. Are you seeing an error? What's your use case? -Toshio On Dec 5, 2017 4:37 AM, "Veena"

Re: [ansible-project] Ansible Galaxy pip Dependencies

Typically you make it the first task in your role. -Toshio On Dec 1, 2017 4:17 PM, "Andrew Vaughan" wrote: Hello all, I have a plugin that's included with a role I intend for Ansible Galaxy. https://galaxy.ansible.com/andrewvaughan/ansible-prompt/ I need, in this

[ansible-project] Ansible 2.4.2 has been released

On behalf of the entire Ansible open source community, we are very happy to announce that Ansible 2.4.2 has been released! This release includes many bugfixes to the 2.4 codebase. For full details, please see the Changelog: https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md As

Re: [ansible-project] register module help

The debug module will help with displaying it and the assert module may be what you want for checking (although there are many other ways to do the latter as well) -toshio On Nov 26, 2017 7:11 PM, "Viju Venugopal" wrote: > – name: verify application/database processes

Re: [ansible-project] ansible 1.9.4 to 2.4.1.0 migration issue

Try nodes[hostname_mounts]["yumextra"] -Toshio On Nov 26, 2017 7:00 PM, "George V" wrote: Hi all, I have been avoiding to upgrade Ansible 1.9.4 on Centos 6 for the past few months, however since the upgrade project is again on my desk, I am actively working through the

Re: [ansible-project] rpmbuild of ansible tarball results in error: line 9: Illegal char '$' in: Version: $VERSION

This looks like you aren't getting the tarballs from the official source: https://releases.ansible.com/ansible/ Note that we also are building nightly rpms (repositories for centos and fedora). Look in https://releases.ansible.com/ansible/rpm -Toshio On Nov 23, 2017 4:40 PM, "Ki-Hyun Sung"

Re: [ansible-project] Ansible - copy between servers

With one exception, ansible is all communication between the controller (where you run the ansible-playbook command) and the managed machines. So using copy you'd need to first fetch the remote files to the controller and then copy them out to the other machines. The one exception is the

Re: [ansible-project] Yum module update_cache doesn't work for RHEL in ansible 2.4.0.0

It does. From your description, it sounds like the RHEL repository has a packageset that's generating conflicts in your install. the update_cache is likely just making the error in the repository visible. CentOS and RHEL pull from different repositories and don't always have the same set of

Re: [ansible-project] Re: pytest arugment error

You need to pip install the test requirements as well. On Nov 6, 2017 4:15 AM, "Jae Kim" wrote: > I had executed >> >> > >> . hacking/env-setup >> >> And then I executed > pytest -r a --fulltrace --color yes ./mymoduletest/my_new_test_ > module.py >

Re: [ansible-project] Re: pytest error message

That depends. Did you install ansible into system site-packages? Or did you check it out from source? On Nov 5, 2017 6:02 PM, "Jae Kim" wrote: > > > $PYTHONPATH is empty. Should this be filled in with something? > > -- > You received this message because you are subscribed

Re: [ansible-project] Re: pytest arugment error

You need to follow the other steps in that page to install the test dependencies, then. Just running the single pytest step won't set up the environment to run the tests. On Nov 5, 2017 5:10 PM, "Jae Kim" wrote: > > It is a single step. > I was following instructions from

Re: [ansible-project] Re: InsecureRequestWarning: Unverified HTTPS

This seems to be coming from urllib3. I don't think we have much affect over it. Since it's a warning it doesn't affect the program's operation. Note that there is a change in 2.4.2 (will be i nthe next tarball) and devel which might remove this usage of urllib3 if you're using python-2.7.9+ so

Re: [ansible-project] How pass an array of dictionaries to my custom module elegantly?

You could probably do: {"/usr/local": "/usr/my/local", "/local/perl": "/usr/my/perl"} That will work as long as order does not matter (if the replacements do not cause there to be more or less of the replacer substrings). If you can't guarantee that, then the list is better, although you can

Re: [ansible-project] pytest arugment error

Could you go through your shells' history and reporter precisely which steps from that page you have performed? It looks like you've missed a step or two. On Nov 2, 2017 5:58 AM, "Jae Kim" wrote: > Hi > > > > Following the command in this manual > >

Re: [ansible-project] pytest error message

How are you arranging for ansible to be in your PYTHONPATH? -Toshio On Nov 2, 2017 5:58 AM, "Jae Kim" wrote: > Hi > > > > When I run the following command > > > > pytest -r a -fulltrace --color yest my_new_test_module.py > > > > I get the following error message. > > > >

  1   2   3   4   >