Katello/Pulp3 Integration meeting

Minutes
#126

2025-04-30

Overview

  • Katello Schedule

Pulp

Katello

  • Katello may start using “internal” repositories to host contents for other Foreman plugins down the road
  • Pulp upgrade to 3.73 is complete
  • DevConf.US booth is proposed - includes Pulp

QE

#127

[Two reports for the price of one!]

2025-05-14

Overview

  • Katello Schedule

Pulp

  • Pulpcore
  • RPM
    • Pulp_rpm 3.30.0 released
      • Repo_gpgcheck, gpgcheck, package_checksum_type, metadata_checksum_type dropped
        • The options don’t do anything, if you try to use them
        • I believe you dropped these a while back (they’ve been deprecated a while) but it’s maybe worth double checking

Katello

  • 4.17 branching today. Will use 3.73 which is now branched: Index of /pulpcore/3.73
    • Be prepared for influx of core/3.73 users
  • Q: setuptools min-version and pulp_python
    • Check in w/ odilhao - Ian will get back to Jitka on this ASAP
    • Other plugins as well?
    • [Ian] We can’t bump up setuptools until it is in RHEL 9, currently we have 68.2 available.
  • Phoenix will prob inherit the Pulp-QE Team
    • Iballou to review attendee list for changes

QE

  • New folk introduced - yay for more QE!

2025-05-28

Overview

  • Katello Schedule

Pulp

Katello

  • Katello 4.17 release in process.
    • core/3.73 and friends
  • Support FlatPak repo “soon”
  • Community question: can one use file: URLs for pulp_ansible?
    • Not unless the API files are available, and prob not then
    • Pulp_ansible expects either “live” API or to be talking to a git-server
  • Confirmed that Phoenix team now contains all Pulp QE as well

QE

  • latest (snap 101) pulp-ansible is python3.12-pulp-ansible-0.24.6-1.el9pc.noarch.rpm
1 Like
#128

2025-06-11

Overview

  • Katello Schedule

Pulp

Katello

  • What happens when Pulp syncs a repository when a package’s modularity state changes? Assume the package has the same checksum as before.
    • A question came up - a non-modular repo was turned modular, but a skip-metadata-check sync seems to have not updated the modularity state
    • Not a great way to deal with this edge-case, alas - “remove all traces and resync”
    • Collides with “Immutable content”
  • Rocky 9 devel repo cannot be synchronized - Support - TheForeman
    • Community wondering if 404s in broken repositories (Rocky) can be worked around somehow
      • “Keep going when the repo is broken” keeps coming up
      • there are reasons we don’t do that (mostly, “you end up with a broken repo you can’t install from and have to go back to the third-party-repo-owner anyway”)
  • Upgrade to Katello 4.17 - katello:correct_repositories fails - #2 by ingcarl - Support - TheForeman
    • RPM client bindings issue: package_signing_fingerprint cannot be nil
    • We are all confused how this is even possible - iballou waiting on user and maybe attempting to reproduce

QE

  • glitch: distribution url of a file-type repo is empty
    • Sounds like a timing-hole between katello/pulp/test
    • Not reliably reproducible
    • Sometimes “waiting” in the test “fixes it” - but maybe not?
      • wait timeout is 120s
    • We are all sad now
2 Likes
#129

A lot of meetings failed to be posted, for various “out of office” reasons - catch up all at once here

2025-08-20

Overview

  • Katello Schedule

Pulp

Katello

QE

  • https://issues.redhat.com/browse/SAT-36451 - first vs next curl (200 vs 404)
    • The fix works on naked-Pulp-instance, fails on first-attempt in katello-install env
    • Pbrochado and vsedmik continue to bang their heads against it
    • [ggainey] this is an edge-case of an edge-case of an error-condition - not worth blocking a release or doing a fire drill on the pulp side right now [pbrochad]+

2025-08-06

Overview

  • Katello Schedule

Pulp

Katello

  • https://issues.redhat.com/browse/SAT-19863 Is there anything pulp can do about this or does this require a redesign on katello’s end. Does pulp replication resolve this if we instead invest in that effort? My understanding is replication creates a new repository for every upstream distribution to be replicated, something our current design driven by katello also does - causing the data to balloon in above tables.
    • Those tables are just Doing Their Job, tracking what content is in which repository. If you make 10 repos where Sat has 1, you’re going to get 10x duplication
  • It’s Pulp & plugins upgrade time for Katello, what versions should we take?
    • core/3.85 is happening Soon (next week?) You may want to be on core/3.84?
    • Having /v4/ available would be a Really Good Thing
  • Any plans to support ostree flatpaks: flathub ?
    • No movement happening on the pulp side of things

QE

  • createrepo_c /pulp_rpm bump - still working on reproducing/testing that change

2025-07-23

Overview

  • Katello Schedule

Pulp

Katello

QE

2025-07-09

Overview

  • Katello Schedule

Pulp

Katello

QE

2025-06-25

Overview

  • Katello Schedule

Pulp

Katello

  • More active planning for /v4/
    • Need some more solidity around “when will /v4/ be ready in Pulp”
    • Aiming at katello/4.19 (releasing end of Q4-ish)

QE

  • Some odd non-reproduceable failures in KS repos sync in provisioning pipelines
    • Need actual pulp-logs to figure out what happened
#130

2025-09-03

Overview

  • Katello Schedule

Pulp

Katello

  • libcomps/SIGSEGV/py3.11 issue
    • New createrepo_c/py3.11 does not show problems in 6.17
    • “Maybe” createrepo_c downgrade addressed the issue
  • One week out from upgrading pulp components (3.85+) into katello/4.19

QE

  • final verifications for Sat-Next (2 in Testing, 1 in RP-upstream (should be in Testing too probably since it’s in 3.73))
#131

2025-09-17

Overview

  • Katello Schedule

Pulp

Katello

  • Thanks for the help with the libcomps issue!
  • Any requests for Pulpcon presentations besides a general Katello update?
    • Examples of good/bad things happening “in the real world” pulp usecases
  • Pulpcore 3.85 upgrade 
  "versions": {
    "deb": "3.7.0",
    "rpm": "3.32.0",
    "core": "3.85.1",
    "file": "3.85.1",
    "ostree": "2.5.0",
    "python": "3.19.0",
    "ansible": "0.28.0",
    "certguard": "3.85.1",
    "container": "2.26.1"
  }

QE

  • no updates
2 Likes
#132

2025-10-29

Overview

  • Katello Schedule

Pulp

Katello

  • https://github.com/pulp/pulp_rpm/issues/4178
    • Pulp needs to figure this out ASAP - bug, or bindings-issue
    • Pedro to work with iballou as needed
    • Options for katello:
      • We fix it
      • Katello monkeypatches the not-working version of pulp-rpm-client
      • Katello pins to a not-broken version of pulp-rpm-client (3.32.2)

QE

  • [INFO] href → PRN automation done
  • [ToDo] pulpcore 3.85 testing

2025-10-15

Overview

  • Katello Schedule

Pulp

Katello

QE

  • no updates - I can donate some time

Build Team

2025-10-01

Overview

  • Katello Schedule

Pulp

  • Pulpcore
  • RPM
    • LOTS of work on evr_t
      • Working to keep it in pgsql so Katello can reuse
    • Downgraded openapi vers to 3.0.1 to address ruby-bindings issue
  • Ansible
  • Pulp Container
  • OSTree
    • Is being used in upstream foreman/katello
    • flathub.org will require this
  • Pulp CLI
  • Pulp Replica
  • PulpCon 2025
    • CfP open til 31-OCT
    • Thanks iballou!

Katello

  • Pulp vulnerability tracking - any demo out there with pulp-services?
    • Katello could benefit from having vulnerabilities in container images (for example) shown for a Quay-like experience.
    • Ping bmbouters and/or hyagi
  • Pulp upgrade is going smoothly!
    • VCR have been run successfully
    • “Weird edge case” testing

QE

#133

2025-11-12

Overview

  • Katello Schedule

Pulp

Katello

  • Add questions to Ian’s Pulpcon proposals in case you’re curious about any interesting use cases for Pulp in Katello.
  • Bindings issue from last time
    • maybe this will get Satellite enough ammo to generate their own bindings sooner rather than later?

QE

  • Avc denials at startup
2 Likes
#134

How to “Add questions to Ian’s Pulpcon proposals”? Simply reply in the main PulpCon thread? It feels like that might get messy.

#135

It might, if there are a lot of them. You can message @iballou directly, too.

#136

(note: 26-NOV mtg cancelled due to PTO)

2025-12-10

Overview

  • Katello Schedule

Pulp

Katello

  • Bindings pinned back due to openapi and polymorphic Ruby bindings

QE

1 Like
#137

2026-01-14

Overview

  • Katello Schedule

Pulp

Katello

  • Wrapping up Sat-Next dev (core/3.85 et al)
  • Working on a bigger bindings-patch to work around the rubygem polymorphic return issue

QE

  • Nothing to report (yay!)
#138

2026-03-04

Overview

  • Katello Schedule

Pulp

Katello

  • Artemis meetup March 23-26th :tada:
  • Pulp-upgrade coming for katello-next, Real Soon Now - core/105?

2026-02-18

Overview

  • Katello Schedule

Pulp

Katello

2026-02-04

Overview

  • Katello Schedule

Pulp

Katello

QE

2026-01-21

Overview

  • Katello Schedule

Pulp

Katello

  • Working on a bigger bindings-patch to work around the rubygem polymorphic return issue
    • Deadline for breaking free from Pulp published bindings on Pulp 4
#139

2026-03-18

Overview

  • Katello Schedule

Pulp

Katello

QE

1 Like
#140

2026-04-01

Overview

  • Katello Schedule

Pulp

  • Pulpcore

  • RPM

  • Ansible

    • Jira
      • Will prob be closed as “nothing Pulp can do to address”, discussion in progress

  • Pulp Container

  • OSTree

  • Pulp CLI

  • Pulp Replica

  • pulp_python

  • Pulp_operator

    • Any future interest from katello/satellite?
      • [Ian] So far I don’t hear plans about running katello in OpenShift, but we are containerizing, so perhaps some day.
      • Current work is around quadlets

  • PQC discussion

  • Will someone volunteer to run the mtg on the 15th?

    • Thank you iballou!

Katello

  • https://github.com/pulp/pulpcore/issues/7533
    • Just accepted into the current sprint
    • Jira
  • New RPMs “real soon now” for next-katello
  • Iballou has been using pulp-oci-images!
  • Work in-progress to move katello away from using our published Ruby bindings
    • And there was Great Rejoicing
    • Would katello upstream a “lite ruby-glue Thing”?
  • Q: is pulp_hugging_face “supported”?
    • A: yes, but only pull-thru support currently
  • Work in-progress to move katello-python off of publications
    • N-1 support makes that….exciting
#141

2026-04-15

Overview

  • Katello Schedule

Pulp

  • Pulpcore
  • 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)
#142

2026-04-15

Overview

  • Katello Schedule

Pulp

  • Pulpcore
  • 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)
#143

2026-04-29

Overview

  • Katello Schedule

Pulp

  • Pulpcore
  • 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
1 Like
#144

2026-05-13

Overview

  • Katello Schedule

Pulp

Katello

QE

  • Containerized-testing in progress, going well so far
#145

2026-07-22

Overview

  • Katello Schedule

Pulp

Katello

  • PQC certs/header-size-limits issue
    • If katello needs help, they will come and ask us
    • Jira: Jira