Majic Projects
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Closed Bug report MAR-122 Installing pip packages via complex version specification fails when using Ansible 2.x
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
    General
  • Targetted for
    2.0.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
    20 minutes
    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

Due to changes in Ansible 2.x in pip module that allow passing in list of packages as name (either comma-separated or as actual list), a number of roles are now failing when deploying pip packages that include complex version specification, for example pip>=9.0.0,<10.0.0.

The following should be done:

  • Update all uses of pip module to default to passing list to name parameter when there is possibility the user/task will use complex version syntax.
Steps to reproduce this issue

Reproduction steps:

  1. Try to set-up server using the common role (that has such a task for updating pip in virtualenv).

Expected results:

  1. pip gets updated in virtual environment.

Actual results:

  1. Error occurs, reporting that <10.0.0 is not a valid package name.
Comments ()
There are no comments
History