Project

Profile

Help

Story #5862

As a user, I do not have to worry about pulpcore being accidentally upgraded by plugins requiring other versions

Added by mdepaulo@redhat.com 7 months ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

33%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:

Description

Consider the following scenario:

1. A user installs Pulp 3.1 with ansible-pulp.
2. When they specify pulp_install_plugins, they unknowingly specify 2 plugins: 1 that requires 3.1, and one that requires 3.0.
3. Pulp gets downgraded from 3.1 to 3.0, and does not function due to different ansible installer logic for the pulpcore version.
4. Even if they overcome the installer logic, the other plugin is now broken.

A similar problem can happen for the container builds.

I believe this should be mitigated by refusing to install a plugin that requires a newer version of pulpcore. It catches the problem early on before it becomes bigger. ("poka-yoke")

I propose a pip constraints file, generated to contain only pulpcore at whatever version of pulpcore installed, immediately after pulpcore is installed. All future pip install tasks will specify the constraints file.
https://pip.pypa.io/en/stable/user_guide/#constraints-files

For our ansible installer, we will use "extra_args" for the constraints argument.
https://docs.ansible.com/ansible/latest/modules/pip_module.html


Subtasks

Task #5863: Generate and use a pulpcore constraints file in ansible-pulpCLOSED - CURRENTRELEASEmdepaulo@redhat.com

Actions
Task #5864: Generate and use a pulpcore constraints file in the pulp-operator pulp containersNEW

Actions
Task #6900: Generate and use a pulpcore constraints file in the all-in-one pulp containersNEW

Actions

Associated revisions

Revision 8bb7db20 View on GitHub
Added by Mike DePaulo 6 months ago

Story: As a user, I do not have to worry about pulpcore being accidentally upgraded by plugins requiring other versions

Fixes: #5863 Generate and use a pulpcore constraints file in ansible-pulp

re: #5862 As a user, I do not have to worry about pulpcore being accidentally upgraded by plugins requiring other versions

re: 5890 [Epic] The ansible-pulp installer needs to handle multiple versions of Pulp

Revision 8bb7db20 View on GitHub
Added by Mike DePaulo 6 months ago

Story: As a user, I do not have to worry about pulpcore being accidentally upgraded by plugins requiring other versions

Fixes: #5863 Generate and use a pulpcore constraints file in ansible-pulp

re: #5862 As a user, I do not have to worry about pulpcore being accidentally upgraded by plugins requiring other versions

re: 5890 [Epic] The ansible-pulp installer needs to handle multiple versions of Pulp

History

#1 Updated by fao89 7 months ago

  • Tags CI/CD added

#2 Updated by mdepaulo@redhat.com 7 months ago

  • Tags deleted (CI/CD)

Please register to edit this issue

Also available in: Atom PDF