Actions
Issue #3026
closed
Getting an error with venv during vagrant up of pulp 3.0 dev environment
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
If you vagrant up on ansible 2.3.1 (the current version in epel7), you get an error:
TASK [dev : Install developer extra-requirements] ******************************
failed: [pulp3_dev] (item=test_requirements.txt) => {"cmd": "/usr/bin/python3 -m venv -p/usr/bin/python3 /home/vagrant/.virtualenvs/pulp", "failed": true, "item": "test_requirements.txt", "msg": "\n:stderr: usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]\n [--upgrade] [--without-pip]\n ENV_DIR [ENV_DIR ...]\nvenv: error: unrecognized arguments: -p/usr/bin/python3\n"}
failed: [pulp3_dev] (item=dev_requirements.txt) => {"cmd": "/usr/bin/python3 -m venv -p/usr/bin/python3 /home/vagrant/.virtualenvs/pulp", "failed": true, "item": "dev_requirements.txt", "msg": "\n:stderr: usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]\n [--upgrade] [--without-pip]\n ENV_DIR [ENV_DIR ...]\nvenv: error: unrecognized arguments: -p/usr/bin/python3\n"}
failed: [pulp3_dev] (item=docs/requirements.txt) => {"cmd": "/usr/bin/python3 -m venv -p/usr/bin/python3 /home/vagrant/.virtualenvs/pulp", "failed": true, "item": "docs/requirements.txt", "msg": "\n:stderr: usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]\n [--upgrade] [--without-pip]\n ENV_DIR [ENV_DIR ...]\nvenv: error: unrecognized arguments: -p/usr/bin/python3\n"}
RUNNING HANDLER [dev : restart sshd] *******************************************
to retry, use: --limit @/home/dadavis/Projects/pulp3-devel/ansible/pulp-from-source.retry
PLAY RECAP *********************************************************************
pulp3_dev : ok=36 changed=25 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
This was fixed in ansible back in June right after 2.3.1 was released:
https://github.com/ansible/ansible/commit/c37aca62efdf9a07d1ca85b5f49af0d39b21045a
Relevant PR:
Actions
.