FEDORA-EPEL-2017-c64e477a67 created by kevin 4 years ago for Fedora EPEL 6
unpushed

Update to 2.4.0 for EPEL6. Additionally drop the python-jmespath requirement here because it causes conflicts on amazon linux.

This update has been submitted for testing by kevin.

4 years ago

This update has been pushed to testing.

4 years ago
User Icon jorti commented & provided feedback 4 years ago
karma

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.

4 years ago
User Icon kevin commented & provided feedback 4 years ago

jorti: can you file a bug on this so we can debug whats going on? I tested vault here and can't duplicate...

User Icon jorti commented & provided feedback 4 years ago

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.

This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes

4 years ago
User Icon geekmug commented & provided feedback 4 years ago
karma

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.

User Icon anonymous commented & provided feedback 4 years ago

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.


Please login to add feedback.

Metadata
Type
enhancement
Karma
-2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 years ago
in testing
4 years ago
BZ#1494640 Ansible 2.3.2 conflict with python27-jmespath
0
0

Automated Test Results