Katello/Pulp3 Integration meeting

[ggainey]

2026-04-15

Overview

• Katello Schedule

Pulp

• Pulpcore
  • All pulpcore changes from last two weeks
  • All merged PRs in the Pulp organization in the last two weeks
  • Q: With the effort to “containerize” katello - are Katello/TheForeman going to continue building RPMs?
    • Ian: Yes, the containers will be based off of our RPMs.
  • pulp_rust now exists. Do you foresee any potential interest?
  • New setting to avoid immediate task timeouts:
    • https://github.com/pulp/pulpcore/pull/7587
    • Backported to 3.85 and 3.105
  • Set default --max-requests 10000 and --max-requests-jitter 500 for API workers to prevent unbounded RSS growth from glibc heap fragmentation over long-lived worker processes. #7482
• RPM
  • New release coming in the next week
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• Pulp_python
  • We’re attempting to remove publications from Python repos in SAT-43537
  • Pulp-python fix needed for publication-less repos SAT-44473
    • This is a single line fix; I can put in a PR later today.
  • There are several other related issues for various Katello-side fixes.

Katello

QE

• pulp-ansible regression Jira
  • versioning issue? (redhat-satellite-3.13.0+1.tar.gz)

[ggainey]

2026-04-29

Overview

• Katello Schedule

Pulp

• Pulpcore
  • All pulpcore changes from last two weeks
  • All merged PRs in the Pulp organization in the last two weeks
• RPM
  • Request from product to support signature verification on sync - will require some Katello integration, medium/long-term goal (2027)
  • Package model now include signing key fingerprints
  • Pulp_rpm 3.36.0 released
  • Client Challenge
  • Making sure you're not a bot!
  • Will add vulnerability report to RPM: Jira
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• Pulp_python
  • 3.19 hasn’t had any backports since September
  • potential backportable things:
    • Fix pull-through failing to check repository when package was not in remote (#1006)
    • Fix pull-through caching failing for improper named packages (#1084)
  • Backports will be released soon in 3.19.3
• Bindings?
  • Is katello generating their own? Or writing a replacement?
    • Katello Hackathon involved starting from OpenAPI spec and writing their own “pulp_glue”
  • Interested in a Rust version of pulp-glue?
    • Iballou really loves the idea of not-maintaining quirks/vers-issues of pulp-glue
    • Would like details of “how would we call this from Ruby”?

Katello

• 3.105 upgrade for 4.21 has gone swimmingly. The upstream upgrade is essentially complete.
  • One remaining upstream PR, then downstream Stuff
• Work remains ongoing for removal of publications from Python-type content.
• Load-balanced Pulps discussion

QE

• Kudos to Gerrod and Daniel for the pulp-container fix for 6.18.5

[ggainey]

2026-05-13

Overview

• Katello Schedule

Pulp

• Pulpcore
  • All pulpcore changes from last two weeks
  • All merged PRs in the Pulp organization in the last two weeks
  • core/3.115 is coming, “soon” (core/3.111 being released today)
  • https://github.com/pulp/pulpcore/issues/7559
    • Allows better control of the amount of temp-storage used by syncs
    • Needs to be consumed by pulp_rpm/pulp_container once released buy core
• RPM
  • Pulp will extract signing_keys on package upload (not sync) and list them on the package
    • https://github.com/pulp/pulp_rpm/issues/4458
    • Both a feature and a bugfix in a non-Katello context
    • Currently only on-upload, but we want to be able to grab this during sync as well
  • Vulnerability report approach for RPM:
    • Define ecosystem by repository (via repository labels)
    • Add extra endpoint to get ecosystem composition for a repository (e.g, can report if a repository has 100% alma linux, rocky, etc)

Katello

• https://github.com/pulp/pulpcore/issues/7705
  • Pedro taking a look, sounds related to the openapi-generator
  • Katello not blocked

QE

• Containerized-testing in progress, going well so far