I tried this update at work in a Sun Ray server running Oracle Linux, so it may have some peculiarities. I'll file a bug on Monday. Go ahead with the update if you are confident it works in a pure rhel6 machine.
I can confirm that on a clean install of RHEL6, this package does not work. In addition to the ansible-vault issue, it also does not run at all ("ImportError: No module named jinja2.exceptions"). The issue can be resolved by installing python-jinja2 (rather than python-jinja2-26), which tells me that the old patch to make ansible use jinja 2.6 is no longer effective.
I think the fix for #1494640 should be applied to the Ansible 2.3 spec and leave this as another change, unless it's immediately obvious to someone else how to get ansible to pickup jinja 2.6 properly.
I am also getting the "No module named jinja2.exceptions" issue with the RPM. Also note that lxml >= 2.3 is needed for the new xml module in Ansible 2.4 and the latest RPM for CentOS 6 is lxml 2.2.
kevin
This update has been submitted for testing by kevin.
This update has been pushed to testing.
I cannot use this version with vaults:
ERROR! ansible-vault requires either the cryptography library (preferred) or a newer version of pycrypto in order to function.
I have these python-crypto packages installed:
python-crypto-2.0.1-22.el6.x86_64 python-crypto2.6-2.6.1-2.el6.x86_64
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
jorti: can you file a bug on this so we can debug whats going on? I tested vault here and can't duplicate...
I tried this update at work in a Sun Ray server running Oracle Linux, so it may have some peculiarities. I'll file a bug on Monday. Go ahead with the update if you are confident it works in a pure rhel6 machine.
https://bugzilla.redhat.com/show_bug.cgi?id=1500600
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
I can confirm that on a clean install of RHEL6, this package does not work. In addition to the ansible-vault issue, it also does not run at all ("ImportError: No module named jinja2.exceptions"). The issue can be resolved by installing python-jinja2 (rather than python-jinja2-26), which tells me that the old patch to make ansible use jinja 2.6 is no longer effective.
I think the fix for #1494640 should be applied to the Ansible 2.3 spec and leave this as another change, unless it's immediately obvious to someone else how to get ansible to pickup jinja 2.6 properly.
This update has been unpushed.
I am also getting the "No module named jinja2.exceptions" issue with the RPM. Also note that lxml >= 2.3 is needed for the new xml module in Ansible 2.4 and the latest RPM for CentOS 6 is lxml 2.2.