Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Bug report MAR-142 Python virtual environment for Python 3 pip requirements check uses wrong interpreter (Python 2)
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
    General
  • Targetted for
    3.1.0
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    2 hours
  • Time spent
    1 hour
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
  • Reproducability
    Always
  • Severity
    Not determined
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description

The common role deploys a mechanism for checking for available updates through the Python virtual environment requirements files.

Functionality depends on having two dedicated Python 2 and Python 3 Python virtual environments for performing the check. During the deployment of common role, however, the Python 3 Python virtual environment is set-up to use the Python 2 interpreter instead of Python 3 interpreter.

Steps to reproduce this issue

Reproduction steps:

  1. Set-up a server using the common role.

  2. Log-in into the server and switch to pipreqcheck user:

    sudo su - pipreqcheck -s /bin/bash
  3. Activate the Python 3 environment

    source ~/virtualenv-py3/bin/activate
  4. Check the Python interpreter version:

    python --version

Expected results:

  1. Python version is reported as 3.x.x.

Actual results:

  1. Python version is reported as 2.x.x.
Todos (0 / 0)
There are no comments