Issue #3026: Getting an error with venv during vagrant up of pulp 3.0 dev environment - Pulp

Actions

Send by e-mail Copy link

Issue #3026

closed

Getting an error with venv during vagrant up of pulp 3.0 dev environment

Added by daviddavis about 7 years ago. Updated almost 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Ichimonji10

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

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:

https://github.com/pulp/devel/pull/86

Actions

Copy link

Updated by daviddavis about 7 years ago

A couple things: it looks like F25 is on 2.3.2 which fixes the problem. Also, rhel-7-server-extras-rpms offers 2.3.2. So really, this just affects CentOS 7 (the OS I am on) which still has 2.3.1 (via epel7).

I've been able to work around this issue by uninstalling the ansible rpm and then installing ansible via pip. We may want to consider closing this as WONTFIX.

Actions

Copy link

Updated by Ichimonji10 about 7 years ago

So really, this just affects CentOS 7 (the OS I am on) which still has 2.3.1 (via epel7).

Note that this issue specifically affects the Ansible control host, not target hosts. So it should still be possible to install Pulp 3 on CentOS 7, so long as the control host has Ansible 2.3.2+.

This bug still sucks. No denying that. :(

Actions

Copy link