March 31, 2021 Overview
- Katello Schedule - 3.18 November 2020 - pulpcore 3.7 - 4.0 branching ~February 2021 (dry-run needed by end-of-Dec) - pulpcore 3.9 - 4.1 branching ~May 2021 - pulpcore 3.10 (or newer) - 4.2 branching ~August 2021 - 4.3 branching ~Nov 2021 Pulp - Pulpcore - 3.12 still on track for 4/6 (or possibly 4/8) - go/no-go meeting tomorrow - Migration fixes - importer/exporter fixes - Katello to look at using 3.12 for 4.1 - Evgeni applied/tested FIPS downstream 3.11 and Things Worked - Jsherrill to coordinate releases that need it - RPM - 3.10 released w/ errata fixes - Mirroring-repodata discussion - can it be used in 4.1? - Ttereshc to investigate whether pulpcore-changes needed - Aiming for pulp_rpm mid-April might work - Pulp3-depsolve-bug - under investigation - Migration - No declared artifact error https://pulp.plan.io/issues/8377 - Issue in the pulpcore, should be solved - Might be causing pulp_container some pain :( - Worked on user reported issues - ggainey testing migration and FIPS - There is an existing issue raised https://pulp.plan.io/issues/8453 - Ansible - Token-auth work postponed - Pulp Container - Docker-push issues being investigated/resolved - Pulp CLI - Shell-mode added - 0.8.0 release ‘soon’ - PulpCon 2021 - Week of November 8-12 Katello - Dogfood testing - Reset, and rerun complete, tanya is going to look into missing rpms - Issue filed to make mongo-batch-size configurable - Maybe do a file-repo migration to reproduce rel-path issues that blocked us? - work on 3.11 upgrade looking good - Ansible collection enhancements ongoing - Auth’d podman pull support on container gateway - Pipeline for live vcr testing with latest bindings QE - Retesting all test scenarios for final snap - Continuing to verify ON_QAs - Reset - https://bugzilla.redhat.com/show_bug.cgi?id=1916759. Seems to work on small scale, but larger db such as customer seems to have issues. Created this bz: https://bugzilla.redhat.com/show_bug.cgi?id=1944375 - Waiting on dogfood once devs are done with their testing - Waiting on fix on customer db from dev so accurate testing on customer db can begin - “Fix” is “get actual RPMs on disk for imported customer DB” - Do we have enough docker testing? - There are docker test-cases, so codepaths are being tested - Running a migration after ‘switchover’ causes some grief - QE, please file katello BZ to handle this more gracefully G -- Grant Gainey Principal Software Engineer, Red Hat System Management Engineering
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-dev