Issue #6669
closedpulp_installer does not support plugins having both the version and the upgrade vars specified
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.
Updated by fao89 over 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 72
Updated by bmbouter over 4 years ago
- Category set to Installer - Moved to GitHub issues
- Tags deleted (
Pulp 3 installer)
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar over 4 years ago
Added by Fabricio Aguiar over 4 years ago
Revision 506d13cc | View on GitHub
Document the conflict between version and upgrade
Updated by Anonymous over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp|506d13cc035e1ee70a32dc91488f5945641f8215.
Updated by dkliban@redhat.com over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Document the conflict between version and upgrade
https://pulp.plan.io/issues/6669 closes #6669