December 08, 2021
Overview
- Katello Schedule
- 3.18
- pulpcore 3.7
- pulp_rpm 3.11
- 4.1, 4.2
- pulpcore 3.14
- pulp_rpm 3.14
- 4.3 ~Nov 2021
- pulpcore 3.16(?)
- pulp_rpm 3.16
- 4.4?
- 3.18
Pulp
- Pulpcore
- 3.17 to release Dec 14th
- Bulk-task delete is merged to be included in 3.17.0
- Hoping to migrate pulpcore issues to github.com/pulp/pulpcore/issues/ next week after 3.17.0 release
- Removing some APIs for managing ContentGuard permissions
- Telemetry working group starting in Jan
- RPM
- Working to improve sync memory-consumption
- Mostly happening in createrepo_c land
- Distribution-tree fun
-
Issue #9566: Create better primary keys for subtrees - RPM Support - Pulp (continued from last week)
- Does this scenario impact Katello? Is a backport needed? (has an impact on implementation)
- Likely yes?
-
Issue #9583: Distribution tree uniqueness constraint is not enough for a suboptimal .treeinfo - RPM Support - Pulp (continued from last week)
- No change
-
Issue #9566: Create better primary keys for subtrees - RPM Support - Pulp (continued from last week)
- Working to improve sync memory-consumption
- Migration
- 0.11.7 is out
- Includes a fix for importer migration on re-runs Backport #9612: Backport #8968 "'NoneType' object has no attribute 'delete'" during migration to 0.11.z - Migration Plugin - Pulp
- Pulp_deb working on deb-2to3
- ttereshc to share diffs w/ katello
- 0.11.7 is out
- Ansible
- Pulp Container
-
2026277 – null value in column "manifest_id" violates not-null constraint error while syncing RHOSP container images
-
- source containers can be a problem, including rate limiting
- 1845471 – [RFE] Add ability to opt out of mirroring source containers.
- To exclude source container use exclude_tags = [‘latest’, ‘*-source’]
- Discussion around how katello/pulp3 could cooperate on how to exclude src-containers
-
-
2026277 – null value in column "manifest_id" violates not-null constraint error while syncing RHOSP container images
- OSTree
- Pulp CLI
Katello
- Switching to sync policy in progress
- May backport downstream-only? Maybe?
- “Let’s backport correctly” seems to be the consensus
- Adding ostree testing to nightly/release pipeline
- Tried out new openapi version bindings, failed to build properly
- Question: https://bugzilla.redhat.com/showhttps://bugzilla.redhat.com/show_bug.cgi?id=2024963_bug.cgi?id=2024963
QE
- Next-X snap 1.1 preview/test
- Next-Y automation failure fixes
- Watching pulpcon pulp testing and adding feedback
Build Team
- No report