Story #5891
closed
Story #5890: [Epic] The ansible-pulp installer needs to handle multiple versions of Pulp
As a user, I can use ansible-pulp to perform a micro update to Pulp 3
100%
Description
This task is to cover the use-case of a user having say Pulp 3.0.0 installed, but running ansible-pulp to update it to 3.0.1.
Required changes that have been identified:
1. Providing a variable on whether to update pulp or not during pip / pypi install.
2. Making sure the handlers are attached to all the necessary tasks, such as pip install/update tasks:
example of 1 handler: https://github.com/pulp/ansible-pulp/search?q=%22Restart+pulpcore-api.service%22&unscoped_q=%22Restart+pulpcore-api.service%22
Updated by mdepaulo@redhat.com about 5 years ago
- Assignee set to mdepaulo@redhat.com
- Sprint Candidate changed from No to Yes
- Sprint set to Sprint 63
Added by Mike DePaulo almost 5 years ago
Added by Mike DePaulo almost 5 years ago
Revision 0c0f33f8 | View on GitHub
Story: As a user, I can use ansible-pulp to perform a micro update to Pulp 3
Implementation includes:
- Variables for controlling pip upgrading or not for pulpcore and the plugins.
- Adding handler for restarting Pulp on pip changes.
- Fixing the changed_when condition for pip install tasks.
fixes: #5891 As a user, I can use ansible-pulp to perform a micro update to Pulp 3 https://pulp.plan.io/issues/5891
Fix handlers
Updated by Anonymous almost 5 years ago
- Status changed from NEW to MODIFIED
- % Done changed from 0 to 100
Applied in changeset ansible-pulp|0c0f33f84b663d0e0ebd177767fbee29262776a8.
Updated by mdepaulo@redhat.com almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
ansible-pulp 3.0.1 has this.
.
Story: As a user, I can use ansible-pulp to perform a micro update to Pulp 3
Implementation includes:
fixes: #5891 As a user, I can use ansible-pulp to perform a micro update to Pulp 3 https://pulp.plan.io/issues/5891
Fix handlers