Project

General

Profile

Actions

Bug #35934

closed

Upgrade to Pulpcore 3.22

Added by Ian Ballou almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Tooling
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

For the Katello code base, this will involve:
1) Upgrade to Pulpcore 3.22 (with new plugins) via pip if necessary (RPMs are better if they're built).
2) Run the Pulpcore tests live without yet updating the client bindings.
-> `mode=all bundle exec rake test:katello:test:pulpcore`
3) If the tests all pass, then we can upgrade to Pulpcore 3.22 without worrying about the client bindings being updated immediately.
-> If any tests aren't passing and they aren't fixed by updating the client bindings, then you've likely found a Pulp bug. File it and decide if it should block the upgrade.
4) Now update the client bindings to the correct versions and rerecord the VCRs with the same command.
5) Create a PR but do not merge it. We need to create the packaging PRs first. This gist should help: https://gist.github.com/ianballou/0094a8585dc39a6aa9c7c427e64f377d

Request: https://community.theforeman.org/t/request-for-pulpcore-3-22-builds/31877

Versions (so far)

Pulpcore 3.22.latest
Pulp-rpm 3.18.latest
Pulp-container 2.14.latest
Pulp-ansible 0.16.latest
Pulp-file 1.11.latest
Pulp-python 3.8.latest
Pulp-deb 2.20.latest
Pulp-ostree 2.0.latest
Pulp-certguard 1.5.latest

Actions

Also available in: Atom PDF