JB-ux
commented
5 years ago I had ran into this same issue. Not sure of the fix, but a workaround that I found was updating the file in
Changed this:
- name: minemeld virtualenv command: virtualenv "{{venv_directory}}" -p "{{python_executable}}" creates="{{venv_directory}}"
To this:
- name: minemeld virtualenv command: virtualenv "{{venv_directory}}" -p "/usr/bin/python" creates="{{venv_directory}}"
The install was able to go all the way through after that.
It seemed that building on CentOS 7 failed at the below stage. My CentOS is updated to the most recent update (14th April 2019) and zlib + zlib devel are present on my system.
TASK [minemeld : virtualenv] ** ok: [127.0.0.1]
TASK [minemeld : minemeld virtualenv] ***** fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": ["virtualenv", "/opt/minemeld/engine/current", "-p", "/usr/local/bin/python2.7"], "delta": "0:00:00.061103", "end": "2019-04-14 18:41:04.092098", "msg": "non-zero return code", "rc": 1, "start": "2019-04-14 18:41:04.030995", "stderr": "Traceback (most recent call last):\n File \"/usr/lib/python2.7/site-packages/virtualenv.py\", line 37, in\n import zlib\nImportError: No module named zlib", "stderr_lines": ["Traceback (most recent call last):", " File \"/usr/lib/python2.7/site-packages/virtualenv.py\", line 37, in ", " import zlib", "ImportError: No module named zlib"], "stdout": "Running virtualenv with interpreter /usr/local/bin/python2.7", "stdout_lines": ["Running virtualenv with interpreter /usr/local/bin/python2.7"]}
to retry, use: --limit @/home/tarcadmin/minemeld-ansible/local.retry
PLAY RECAP **** 127.0.0.1 : ok=33 changed=17 unreachable=0 failed=1