Bug 1353200
| Summary: | [python27] python-virtualenv: os.py:157:makedirs:OSError: [Errno 20] Not a directory: 'ansible/lib' | ||
|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Branislav Náter <bnater> |
| Component: | python-virtualenv | Assignee: | Python Maintainers <python-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Branislav Náter <bnater> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | python27 | CC: | cstratak, djez, isenfeld, jberan, jkejda, pviktori, qe-baseos-apps, rpiddapa, torsava |
| Target Milestone: | --- | ||
| Target Release: | 2.4 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python27-python-virtualenv-13.1.0-2.el7 python27-python-virtualenv-13.1.0-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: When virtualenv is run with a parameter that is a path to an existing file (not a directory).
Consequence: virtualenv will crash with a complicated traceback.
Fix: virtualenv will display a customized error message in lieu of crashing.
Result: "ERROR: File already exists and is not a directory.
Please provide a different path or delete the file."
|
Story Points: | --- |
| Clone Of: | 1306513 | Environment: | |
| Last Closed: | 2017-04-26 10:20:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Petr Viktorin (pviktori)
2016-07-07 08:01:08 UTC
Verified on python27-python-virtualenv-13.1.0-2.el6 and python27-python-virtualenv-13.1.0-2.el7 packages. python-virtualenv now provides reasonable error message when file already exists. TCMS test case runs: https://tcms.engineering.redhat.com/run/305838/#caserun_15308644 https://tcms.engineering.redhat.com/run/305839/#caserun_15308814 https://tcms.engineering.redhat.com/run/305850/#caserun_15309980 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1162 |