Ansible 1.9.0 rc1 is now available

Archives Ansible Project
1

Hi all, we’ve just tagged the rc1 release for 1.9, which you can test as follows:

To test from source, simply clone the git repository (if you haven’t already) and do the following:

$ git checkout v1.9.0-0.1.rc1
$ . hacking/env-setup

After which time you can run ansible and ansible-playbook like normal. If you’re not familiar with the hacking/env-setup script, please refer to the documentation here:

http://docs.ansible.com/intro_installation.html#running-from-source

To make an RPM or DEB with which to test, do the following:

$ git checkout v1.9.0-0.1.rc1

for RPMs

$ OFFICIAL=yes make rpm

for DEBs

$ OFFICIAL=yes make deb

If you discover any errors related to this release candidate, please open a Github issue and be sure to mention you’re testing against the release candidate.

Thanks!

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

2

​Also, after the checkout, don't forget to run git submodule update.​

3

Am I doing something wrong?

[(rmts/nsbl/stbl-1.9)] serge@goldorak:~/src/ansible/ansible$ git co v1.9.0-0.1.rc1
HEAD is now at bce4bb2… preliminary privlege escalation unification + pbrun - …
[(rmts/nsbl/stbl-1.9)] serge@goldorak:~/src/ansible/ansible$ git submodule update
[(rmts/nsbl/stbl-1.9)] serge@goldorak:~/src/ansible/ansible$ make tests
…
test_with_tag (TestDocker.DockerSplitImageTagTestCase) … ok
test_with_tag_and_org_name (TestDocker.DockerSplitImageTagTestCase) … ok

4

No, we noticed that too, but decided to go ahead with the release candidate as we weren’t sure if it was simply something that needed to be adjusted in the test due to the PBRun-related changes.

If it’s simply test related, we’ll put the fix in the final release or the next RC so it tests cleanly.

Thanks!

5

Accidentally sent this off list, so let’s try again…

Unrelated, but should the new escalation code really be included in 1.9? I’d think for something with such potentially impactful changes that it should bake for longer than an RC before release.

6

Hi Matt,

We had a lot of requests for pbrun support from some users and customers, and Brian had already done a lot of work on it for the 1.9 release before we had originally changed course and decided to make it a 2.0 feature. However, we decided to make it a stretch goal for 1.9, so users who wanted it would not have to wait until late May or early June when 2.0 would go live. Additionally, since we’re now doing the release candidates, we felt this would help weed out any bugs. We’ve also had a couple of reports of bugs already, so we’ll be doing an rc2 next Tuesday and there’s still plenty of time to test things out. This also tells us that the RC process is working as we intended it to - we do not expect every rc1 to be perfect and consider it an alpha release.

When reviewing the patch, I felt about 80% of it was either a cut/paste replacement of the existing code to use the new variables names, or whitespace cleanup. So despite the size of the patch, it wasn’t quite as impacting as an 800+ line code change might look at first.

Thanks!