Ansible 1.3 and AWX 1.3 Released!

Archives Ansible Project
1

Hi everyone,

I’m very happy to announce that we’ve just released Ansible 1.3 (“Top of the World”) and AWX 1.3!

You can read the full announcement on our blog here:

http://blog.ansibleworks.com/2013/09/13/ansible-1-3-and-awx-1-3-hit-the-streets/

We still need to bump version info in the main repo and get downloads up in pip, so stay tuned for that.
Distributions will update shortly as well. You can always get the latest release at:

http://ansibleworks.com/releases/

Following our release scheme of naming things after Van Halen Songs, the codename of Ansible 1.4 is “Could This Be Magic” off of “Women and Children First”.

Thank you all!

2

Just a quick update – Ansible 1.3 is now available in pip.

3

Hi all, just a quick heads-up. A bug was found in the new accelerate mode when gathering facts (the setup module is always executed via sudo, regardless of the user/sudo_user setting), so we will be releasing 1.3.1 early next week. In the meantime, if you are using the new accelerated mode, the workarounds are to either disable fact gathering via or to ensure that the requiretty option is removed from your sudoers configuration.

Thanks!

4

I’m sill getting 1.2.3 from pip:
$ pip install ansible
Downloading/unpacking ansible
Downloading ansible-1.2.3.tar.gz (359kB): 359kB downloaded

5

Might be a mirroring or caching issue somewhere?

If I take a look at https://pypi.python.org/pypi/ansible, it shows 1.3.0 is available.

6

Is there a projection on how long until macports is updated?

port install ansible
—> Computing dependencies for ansible
—> Fetching archive for ansible
—> Attempting to fetch ansible-1.2.2_0.darwin_12.noarch.tbz2 from http://packages.macports.org/ansible

7

We don’t maintain that one.

Best to contact the maintainer.

8

Yes, PyPI is behind a CDN nowadays. There have been issues.

I’m in the same boat, waiting for 1.3 to pop up on PyPI (still no luck). What I find funny is that here1 it’s said “There will now be a delay of several minutes in some cases between updating a package and having it be installable” and it’s been a few days now. :stuck_out_tongue:

9

Hm, an observation:

https://crate.io/packages/ansible/1.3.0/ displays “No Package Hosting”

and yet, https://crate.io/packages/ansible/1.2.3/ displays: “Package is hosted on PyPI”.

I don’t actually know what this means, just something that caught my eye.

10

I can confirm that. I’ve been trying to upgrade for a few days now and I can’t get 1.3.0
Here’s what I get;

$ pip search ansible
ansible - Radically simple IT automation
INSTALLED: 1.2.3
LATEST: 1.3.0

$ pip install --upgrade ansible==1.3.0
Downloading/unpacking ansible==1.3.0
Could not find a version that satisfies the requirement ansible==1.3.0 (from versions: 1.2.1, 1.2, 1.2.2, 1.0, 1.1, 1.2.3)
Cleaning up…
No distributions matching the version for ansible==1.3.0

11

We’ll investigate.

Thanks.

12

Ok, I checked PyPi and it appears the upload of the tarball had failed without sharing a warning, despite updating the record.

I’ve added the tarball manually and it should show up soon.

13

Michael, care complaining about it upstream? (https://twitter.com/dstufft/status/379276526753447936)

Maybe it’s a bug or something to be improved.

14

Thanks…

I don’t have the original output of what may have happened then to be able to reproduce it.

I might have honestly also run the wrong command.

It’s all good and fixed now :slight_smile:

15

Minor update – initially the file got uploaded with a wrong filename.

If you tried previously and did not have happy results, try again now.

16

when is the epel repository going to be updated?

17

It’s already in epel testing. Once something is in epel testing the package will appear in EPEL in a couple of weeks.

My recommendation is to go ahead and use epel testing, as we’re likely going to bump 1.3.0 shortly (today, hopefully) to fix a small thing with accelerate mode trying to use sudo when it doesn’t need to.

–Michael

18

Hi,

I’m using the AWX repo from :
deb http://ansibleworks.com/releases/awx/deb precise non-free

The 1.3 package broke the current install and destroyed the “public” folder containing the static files for AWX…
I can also see some missconfiguration in the apache vhost file for SSL.
Any idea ?

19

Hi,

Can you please email support@ansibleworks.com and we will get you some
help? The list is just for open-source Ansible discussion. Thanks!

-Tim

20

Right, this is a list for the OSS project only.

Just to share with the list, there should be no problems with the upgrade path, and the “public” directory is not something any user content exists on.

Nobody should have any problems upgrading, let us know if you do by emailing support.

vhost has also been well tested on both Ubuntu and CentOS.