Project

Profile

Help

Issue #6669

closed

pulp_installer does not support plugins having both the version and the upgrade vars specified

Added by mdepaulo@redhat.com over 4 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 73
Quarter:

Description

This is a commonly reported issue by users.

If a user specifies both the version and upgrade vars for a plugin under pulp_install_plugins, pulp_installer fails.

(This might be only when the upgrade var is set to true).

This is because even though a command like pip install --upgrade pulp-file=0.3.0 is valid, the ansible pip module refuses to let you specify version and state=latest (state=latest maps to pip --upgrade, and to our upgrade: true).

I was hoping that specifying both would upgrade all dependencies.

We should probably address this omitting or specifying false for upgrade, whenever version is set.

Make sure to update the pulp role's README.md for this.

Also available in: Atom PDF