Katello/Pulp3 Integration meeting

[ggainey]

2025-03-05

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • [Ian] Re: What are downstream’s plans for upgrading Postgres beyond 13?
    • As per the platform team, PostgreSQL 13 will continue to be supported in RHEL 9 until 2032, so “we have time”
    • Red Hat Enterprise Linux Application Streams Life Cycle - Red Hat Customer Portal → search for postgresql in the page under RHEL 9
  • core/3.73 released
    • Would Very Much Like katello to use that (at least)
    • Iballou: current katello experiments w/ 3.70 are “just working”
    • N-1 capsule sync “just works” (?!?)
    • As long as needed-plugins are 3.73-compat in their released versions then iballou can update
• RPM
  • rpm/3.28 Changelog
• Ansible
  • AC deadlock fix: https://github.com/pulp/pulp_ansible/pull/2132
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Tell katello “things that we’d like to use postgres-16 for”
• Switch to relying on PRNs is recognized as “would be a great idea” by PM - but “not a top priority”

QE

• testing Gerrod’s fix for AC deadlock, results should be around midnight
• Sat-next-Z signed-off with [PULP-296] Fixup running tasks that are not unblocked by mdellweg · Pull Request #6223 · pulp/pulpcore · GitHub inside

[ggainey]

2025-03-19

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.74 released
  • ACS performance enhancement released/backported
    • We really need some way to reproduce the memory issue w/ ACS, to get a handle on it
    • Needs a satellite-box to repro - “pulp by itself” doesn’t currently show. vsedmik/dalley to work together on that
  • Currently core/3.73 is the “supported branch” post-3.69 - let us know if that’s not right!
    • core/3.73 is A Good Idea
• RPM
  • rpm/3.29 released
  • Wants createrepo_c/1.2.1+ to solve a FIPS-compliance issue reported by community
    • Backported to 3.28
    • Lots of discussion ensues
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Working to reproduce https://github.com/pulp/pulpcore/issues/6309#issuecomment-2710843452 again
• Upgrades post-3.70 going smoothly, waiting on packaging for Stuff
• Discussion re downstream-desired Jiras
  • https://issues.redhat.com/browse/PULP-278 - to be done at installer - iballou to move related jira appropriately, ggainey to close pulp issue

QE

• TY for the pulp-ansible-0.21.10 release (should come into Sat 6.16.4 next snap)
• Spinning up an instance for dalley’s ACS-memory-issue testing
• How to update field using pulp-cli

[ggainey]

2025-04-02

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.75 released, a number of backports to 3.73 also released
• RPM
  • https://github.com/pulp/pulp_rpm/issues/3927 (chunked-upload issue)
    • Katello maybe affected? CIQ contributing a fix
      • Katello NOT affected, only affects signing
• Ansible
• Pulp Container
• OSTree
  • Update to allow more-recent PyGObject - ggainey to insure released
• Pulp CLI
• Pulp Replica

Katello

• https://issues.redhat.com/browse/SAT-32421
  • Discovered the day before the proposed next-Y signoff, but it looks like we’ll get at least one more snap
  • Discussing it with Gerrod
  • container/2.23 and 2.24 might be consumable? Diff is less scary than it sounds
    • Only non-bugfix changes are migration squashing and partial domain support (and the bugfix changes are in 2.22 also)
  • Can we get away with backporting the migration in this special case?
  • Pulp needs to get https://issues.redhat.com/browse/PULP-449 into current sprint
• Katello planning to allow certificate-authentication - does Pulp have any plans for cert-auth for api-workers?
  • Pulp has done zero investigation

QE

• Please fix the problem raised above, Soon