Katello/Pulp3 Integration meeting

[ggainey]

2023-07-26

Overview

• Katello Schedule

Pulp

• Pulpcore

  • Query of all changes from last two weeks
  • Z-releases (including migration-fixes)
  • Gunicorn memory-leak fix released
    • 2122872 – pulpcore-api gunicorn process consumes high memory
    • https://github.com/theforeman/puppet-pulpcore/pull/295 - relaxes the number of restarts once ‘2872 is released

• RPM

  • Q: what version of pulp_rpm is being looked at for katello/4.10?
    • Impacts what we do nightly-tests on and backports-to
    • Also - file/container/ansible?
    • Discussion ensues
    • See Request for Pulpcore 3.28 builds - Releases - TheForeman for initial request
    • Will prob choose “most current release” of plugins at the 4.10 branch point (Aug 22ish) and core/3.28

• Ansible

• Pulp Container

  • [ipanova] https://github.com/pulp/pulp_container/issues/1329
    • In attempt to fix Repair API, we broke pulp-to-pulp sync aka SatServer→Capsule sync
    • 2223707 – Capsule docker sync fails with 406

• OSTree

• Pulp CLI

  • Pulp-replication commands merged
  • Prob should do a cli release “soon”

• Pulp Replica

  • Back under active support/development w/ dkliban back

• BZ process

  • See dralley’s ping on internal Slack RE BZs-in-POST that may be further along

Katello

• Does ACS refresh have an optimized option like remote syncs? - 2219885 – Satellite using the feature 'Alternate Content Source' is getting errors
  • By default, yes
  • Katello to do some testing around this BZ
• Pulpcore 3.28 repo in progress
  • We’ll be testing upgrading to 3.28 with Katello soon
  • #soon!! - Pulp r excite

QE

• RE ipanova’s pulp_container issue - QE tests are passing without?
  • Vsedmik to check test-versions, maybe poke ipanova as/if needed
• https://bugzilla.redhat.com/show_bug.cgi?id=2142689
  • May not be reproducible any more - vsedmik to do some investigation
  • Will prob eventually close? Depends on Sat-Current-Y testing

[ggainey]

2023-08-09

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • 3.30 released
  • A lot of performance-related investigation/fixes going on
• RPM
  • See above RE performance investigations
  • 2219885 – Satellite using the feature 'Alternate Content Source' is getting errors investigation (ACS refresh fun)
• Ansible
• Pulp Container
  • 2.16 released w/ flatpak support
• OSTree
• Pulp CLI
  • 0.21 released w/ pulp-replica support
• Pulp Replica
  • Some tls-fixes released

Katello

• core/3.28 - all katello/4.10 tests run, hit one unreproducible error
  • https://github.com/pulp/pulp_rpm/issues/3223
    • Not gonna be hi-prio unless/until we see it again
  • Hoping to bump pulp_container to 2.16 next

QE

• some help needed to reproduce/test 2125366 – Capsule sync fails with Error: It is not possible to add more than one advisory with the same id to a repository version

  • We have an upstream test - let’s get the link for QE to look at

• How to track 2122872 and 2229788 (gunicorn memory leak Fun)

  • 2122872 originally had a workaround that we were going to move forwards with
    • It was cloned to 6.13.2 as 211957 and pushed, now CLOSED-ERRATA
    • Then we found a better fix, and we want to push that to Next-Z? And Sat-Next
    • We also intend to revert the workaround as it’s no longer needed
      • The PR that does the reverting (i.e. we want this commit): https://github.com/theforeman/puppet-pulpcore/pull/295
  • 2229788 was created for the “actual” fix
  • TL;DR how should this be tracked
    • Dalley suggestion:
      • Leave 2122872 tracking the “meta-issue” of gunicorn memory consumption, including the new lru_cache fix, and the reversion, for Sat-Next
      • Use 2122872 to track the improved fix and the reversion for Next-Z?
      • In both cases, we just test that the gunicorn memory consumption issue is resolved as expected
  • ‘2872 - used to handle the mitigation/restart Fun
  • ‘9788 - used for the ‘real’ fix
  • ‘1957 - cloned ‘2872 mitigation for 6.13 release
  • ‘9788 won’t fix 6.11/6.12 cases (since it’s fixing something that didn’t happen until 6.13)
  • What we settled on:
    • Keep 9788 for separately tracking the lru_cache fix (and set flags to clone it for 6.13)
    • Create a new bug to track the relaxed installer defaults (6.13 cloning optional)
      • Created 2230584
      • flags: 6.14.0?, 6.13.z?
    • QE these together with the original bug, so that QE effort is not duplicated
      • (the “actual” fix + relaxation) for each release
    • Email Brad, Justin and Vijay Singh (QE mngrs), Shweta (QE contact for already delivered mitigations on 6.13) and Vlad (QE just for tracking), and Odilon (delivery) so everyone knows what to expect
    • The new BZs should be triaged on Aug 10th triage meeting, Vlad or William will provide the info.

[ggainey]

2023-09-06

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.33 released
    • Adds complex-filters - see Changelog — Pulp Project 3.33.0 documentation
  • import/export performance investigations happening
• RPM
  • Progress being made on Oracle + RHEL sync data corruption https://bugzilla.redhat.com/show_bug.cgi?id=2232500
    • Probably no patch for existing releases, but we can fix it going forwards
    • Some questions about how the migration should work
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• Virtual PulpCon: November 6-10, 2023, 0800-1200 GMT-5 (US EDT)
  • CfP ends 13-SEP
  • Can we get any talks from Katello?
    • [Ian] we’ll think of something!
    • Maybe fs-exporter from paji?
    • container-push design in katello?
  • Add to the CfP page!

Katello

• Quba42 and pulp_deb/3.0
  • discussion/investigation in progress Right Now
  • Trying to see if we can fit into katello/4.10 release
  • Stay tuned!
• BZ RE “tell users if module-streams have expired”?
  • Is this even available? (looks like Not)

QE

• Couple BZs still being verified

[ggainey]

(Catching up on notes - usual poster was unavailable)

2023-10-18

Overview

• Katello Schedule

Pulp

• Pulpcore

  • Query of all changes from last two weeks
  • Lots of performance-improvements in import/export merged and backported
  • See 4545 - we are working to no longer “reassemble” export-files on import
    • Requesting input from katello
    • QE: there may be a test specifically aimed at interrupting the import-process - vsedmik to review
  • [lmjachky] Katello: What are we going to do about this: Slow content proxy sync - #26 by lubosmj - Support - TheForeman
    • User reverted https://github.com/pulp/pulpcore/pull/4275 and things got better
    • User is on postgres12, we can’t reproduce but we’re on pgres-13
    • lmjachky/iballou to work together on getting older-pgres test sys up

• RPM

• Ansible

• Pulp Container

• OSTree

• Pulp CLI

• Pulp Replica

Katello

• 4.10 GA “imminent”, a lot of new core/3.28 users incoming!
• 4.11 will be branching Real Soon Now
  • Once that happens, will be upgrading Pulp again
  • ggainey to update support-matrix - 4.11 versions same as 4.10

QE

• Reviewed import/export perf-BZs from a test standpoint, looks good
  • QE ready to get the releases w/ the fixes

2023-10-04

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Import/export performance fixes
• RPM
  • Zstd metadata support moving forwards:
    • Now a BZ open as it is in the wild 2241934 – After upstream repo switched to zst compression, Satellite 6.12.5.1 unable to sync
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Community support threads:
  • Slow content proxy sync - #19 by gvde - Support - TheForeman
  • Two streams with matching NSVCA - #11 by leziri - Support - TheForeman
    • Likely workaround: republish using “mirror complete”

2023-09-20

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Potential performance regression? Slow content proxy sync - #7 by gvde - Support - TheForeman
    • Comparative performance tests would be helpful for catching these issues?
  • Lots of work on import/export performance
• RPM
  • Zstd metadata support
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Need backport of https://github.com/pulp/pulp_ansible/pull/1561/ to fix syncing ansible content to smart proxies for Katello 4.10 (GAing next week)
  • Chatting with Gerrod about it now, awaiting opinions from Matthias
  • A backport to 0.18.0 would be ideal, but we could work with a release if it’s compatible with Pulpcore 3.28.

[ggainey]

2023-11-01

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • 3.40 released! (requires plugin-updates to be compatible, happening this week)
    • Pulp_file now delivered as part-of pulpcore
    • Pulp_file will start versioning same-as core (ie jump to 3.40)
    • Need to verify/have solid answer that client-api rpm/gems still work
  • If katello/4.11 runs into probs w/ core/3.40 will drop back to core/3.39 and friends
  • In core/3.45, pulp-certguard will also be delivered as part of pulpcore
• RPM
  • New Pulp team member joining today - Pedro Pessoa
  • Pulp_rpm 3.23.0 released
    • Small update, one unbackportable BZ addressed here
      • 2232500 – Synchronizing Oracle Linux 9 AppStream breaks modularity in CVs with filters
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• PulpCon is NEXT WEEK!
  • PulpCon 2023 Schedule - HackMD

Katello

• PulpCon schedule shared to the rest of the team, yay!
• Pulpcore upgrade
  • Trying to get 3.40 into katello/4.11
  • Timeline is VERY SHORT
  • Client-api needs to work for N-1
  • any surprises will prob abort the effort

QE

• Concern about core-update and N/N-1 api access requirement?
  • Iballou to experiment pre-snap/pre-QE
  • Vsedmik to coord w/iballou to get test-scenarios run automatically
  • Dalley proposes to run old-bindings against new-core and give feedback
  • Also katello VCR runs

Build Team

• If core/3.40 is a Bridge Too Far, should we just choose core/3.39 from the start?

[ggainey]

2023-11-15

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • finding/fixing some subtle side-effects of merging pulp_file into core
  • pulp_file/1.6 released as a “dummy” package
  • Release in progress to address a BZ/issue
    • 2249847 – Syncing file:// repos can delete the original files
• RPM
  • Onboarding a new team member!
  • PR open to deprecate pkg/metadata csum-type, merge into one
    • Evaluate whether we really need to support specifying "metadata_checksum_type" and "package_checksum_type" separately · Issue #2480 · pulp/pulp_rpm · GitHub
    • https://github.com/pulp/pulp_rpm/pull/3306
    • Katello has a selector, and so will be affected
    • Currently katello only allows sha256/sha1
    • Not backportable, so will only impact future satellites
    • No real need to continue providing the option for sha1, so the decision is whether to remove the option entirely or replace sha1 option with sha512
      • Personally I feel sha512 support isn’t necessary and we’ve had no customer demand
• Ansible
• Pulp Container
  • [lmjachky] hosting bootable RHEL images in Pulp/Satellite - katello will need to support building images and pushing images into Pulp.
    • pulp-container has the support now (specifically, container-push)
    • Katello: “push” already in-plan for future release
    • Image-building support should be investigated/integrated into katello
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• “Goin crazy on core/3.39 pkg-building Fun”
• Final fit-and-finish in progress on that effort

QE

• “So far so good”
• Testing against N-1 setup w/ core/3.39, also “so far so good”

[ggainey]

2023-12-13

Overview

• Katello Schedule

Pulp

• Last meeting of the year!
  • Is this meeting still useful?
  • Is the cadence still useful?
  • Does the meeting time still work?
  • ggainey to schedule 6 months in 2024, if so
• Pulpcore
  • Query of all changes from last two weeks
  • Div-by-zero during import?
    • Fix is simple but improving tests before merging
    • How urgent is getting this fix out?
      • QE would like a fix “soon”
      • Next snap is next Weds - can we get it done before?
      • Let’s just take the fix for now, get an issue open for the test-work
  • Investigation ongoing for 2253381 – Failed incremental CV import shows error: duplicate key value violates unique constraint "rpm_updatecollectionname_name_update_record_id_6ef33bed_uniq"
• RPM
  • Zstd publishing support added
    • Works for RHEL8.1+/9/10 (nut not RHEL7, no yum support there)
    • Not merged/released into pulp_rpm
    • Not the default, just a new option available
    • Could be exposed by a katello-UI widget “at some point”
  • Publishing with checksums weaker than sha256 removed
    • see 13-NOV minutes
    • Will be in pulp_rpm/3.25
    • Katello will need to decide what to do w/ the csum-choice-pulldown at publish button
    • EL5 may not support sha256 - but it has other, larger, issues w/ “modern” katello
    • Mirroring metadata works fine for older/ancient distributions
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• N-1 problem
  • Is the communication between Satellite and its Capsules isolated at all?
  • There is a decent amount of separation - maybe we can make changes in just-smart-proxy comms to deal with this

Katello

• Pulpcore nightly builds & Katello’s new stricter upgrade plan
  • Pulp upgrade was WAY more than anticipated
  • In future, will select the pulp-release for a branch at the branch-point, or very close to
  • Pretty close to having up-to-date pulpcore “nightly”
  • Env updates (ie, python3.next-X) - even more conservative

QE

• 6.14.next BZs all done
  • Pulp cheers!
• container sync issue - lubos is on it
  • Might be https://github.com/pulp/pulp_container/pull/1133
• zstd 2241934 – After upstream repo switched to zst compression, Satellite 6.12.5.1 unable to sync
  • Fix needs to be released for 6.13 - already available as backports in appropriate upstream branches
  • Vsedmik to bug zstream triage, and/or bbuckingham/odilhao

[ggainey]

2024–01-10

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
• RPM
  • Working on Sat-Next BZs as our priority
  • Dalley out Tuesday - Friday next week
  • 2 weeks before BZ freeze (24-JAN)
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Time to think about Pulp versions for:
  • Katello 4.12 (need decision around Feb 1st)
  • Katello 4.13 / Satellite 6.16
  • Currently at core/3.43, next potential breaking-change release is core/3.55
  • Suggestion: Pick whatever is current as of 30-JAN
    • Are there any features that are not already in Pulp that are desired/required for katello-4.12/13?
    • Iballou to investigate
  • Def need to understand build-implications (if any)
    • Python-version-issues (3.11) already resolved
      • Modularity-fun ensued, but is resolved

QE

• not many updates - Sat-Next BZs under verification - 5 ON_QA / 3 VERIFIED

2024-01-24

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • 3.45 released
    • Certguard now “part of” core, just like pulp_file
  • core/3.28 wasn’t getting backports for Nov/Dec - fixed now, core/3.28.20 released
  • HTTPS proxy support now complete / merged, release incoming for 3.39
• RPM
  • Working through hyu’s suggested patch for 2253381
  • Pedro investigating whether there is anything to do re: 2252662 – satellite-6.11.5.6-1.el7sat.noarch has complete content-view module filter failure for RHEL 8 between 8.8 > 8.9 minor releases
    • There may not be, in which case Sat-Next has one less issue
  • The migration blocking issue turned out to be caused by manual index deletions on both community users
    • • another issue, both remove from Sat-Next
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
• Pulp docs rework
  • See "Unified Docs" Plan - #4 by dkliban

Katello

• It’s unlikely that we’ll be able to squeeze in a Pulp upgrade for Katello 4.12 since time was lost due to shutdown + 4.11 delays
  • Delivery is working on “pulp nightly” and a new Pulp installer method at the same time, which would make building a new version at the same time difficult
  • When Katello 4.12 branches, we will start testing Katello nightly with Pulpcore nightly to make it easier to upgrade for Katello 4.13.
    • Pulp cheers wildly
  • More info: Release Team Meeting 2024-01-17 - #2 by ekohl - Releases - TheForeman
• 2219885 – Satellite using the feature 'Alternate Content Source' is getting errors - blocker for Sat-Next?
  • Discussion ensues
• Using public URLS for testing?
  • Sometimes you need the Filthy Public Repo Data to test edge cases (rpm ecosystem esp)
  • fixtures.pulpproject.org is a good set of “standard” repos to test with
  • QE already uses them for some tests

QE

• we are approx in the first third of Sat-Next verification

[ggainey]

2024-02-07

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • HTTPS proxy support has been verified
    • A new BZ has been filed for Katello - manifest refresh isn’t working 2263159
• RPM
  • 2253381 investigation continues, now w/ reproducer on customer site
  • 2246247 repo-delete can cause a large memory-spike, dalley investigating
  • 2207867 2151657 repositories can contain duplicate NEVRA if the file paths are different
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• next-Y seems to be moving along well, curr-X has been verified
• next-Y+1 features in-progress (repo-repair, container-upload for examples )
  • core/3.39 dev-boxes for katello devs - work in progress
• Flatpak support being discussed

QE

Build Team

[quba42]

@ggainey

pulpcore: HTTPS proxy support has been verified

Can you expand on this? In particular I would be interested in the versions involved.

[ggainey]

This PR Taught https-download to trust system certstore. by ggainey · Pull Request #4951 · pulp/pulpcore · GitHub taught Pulp to know about the system-truststore-certs. Prior to that, trying to access a Remote via an HTTPS proxy that used a different CA than the Remote (which is the usual case!) would fail. (A long time back, you couldn’t even try, because aiohttp didn’t support https-proxies at all until…3.8? Maybe?)

This change requires py3.11 - prior to that, one had to depend on basically monkeypatching an internal attribute to get it to work. See fixes #3036 -Setup the SSL Context correctly for https proxies by parthaa · Pull Request #3038 · pulp/pulpcore · GitHub for what that looked like.

[ggainey]

2024-02-21

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Update the table of versions
    • No changes for 4.12, 4.13 not set yet
• RPM
  • 2253381 fixed and released to All The Branches
• Ansible
• Pulp Container
  • Flatpak support should be done/available for katello to start consuming
  • question: are “flatpak images” different than OCI images?
    • As a user I want to differentiate between different nature of images · Issue #1437 · pulp/pulp_container · GitHub (introducing a flag for the Content ViewSet to better distinguish between flatpak-based or OCI-based images; easier consumption/filtering for Katello)
• OSTree
  • domains/rbac support added
• Pulp CLI
• Pulp Replica

Katello

• Work ongoing to integrate pulp repair on Capsules
• Ansible import BZ: 2262379 – Library import of an Ansible Collection repo fails
  • https://redhat-internal.slack.com/archives/C031713779N/p1706800620522639
• Flatpak support discussion, is being discussed
• Container push is refined and ready to be worked on for Katello 4.13

QE

• sat-Next - 11/13 verified, 2 circled back to DEV
  • 2223069 – Selinux denials are reported after following "Chapter 13. Managing Custom File Type Content" chapter step by step
  • 2263069 – pulp generated config.repo file lacks GPG public key

[ggainey]

2024-03-06

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.49 released
  • Reminder: core/3.55 is coming!
• RPM
  • Investigating some reported issues
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Choosing pulp-versions for katello413
  • Will wait till post-4.12-GA (19-MAR) to choose
  • Will grab whatever-is-newest
• Pulp-container: exposing labels/flags?
  • Pulp hoping to merge the work this week
    • Will update supported branches based on the Katello requirements if they pick up the latest available pulp-container version
  • Should make it into katello/4.14 UI
  • Ping iballou as soon as it’s released

QE

• mostly done with next-Y (two more BZs should land in today’s snap)
• one to be verified in next-Z
• Katello-flatpak-test-support still under discussion

[ggainey]

2024-03-20

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
• RPM
  • What timeout does orphan cleanup use by default?
    • "00000000" modular context chomped to "0" · Issue #3454 · pulp/pulp_rpm · GitHub
  • Looking at 2247646 – Capsule sync gets stuck forever after specific connection issues
• Ansible
• Pulp Container
  • 2.19 released with the labels support (As a user I want to differentiate between different nature of images · Issue #1437 · pulp/pulp_container · GitHub)
    • Will be in katello/4.13
  • NOT SET IN STONE: There is an idea to enable sync by manifests’ digests instead of tags
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Orphaned pulp content - #19 by gvde - Support - TheForeman discussion
• Locking in Katello 4.13 Pulpcore versions imminently
  • Planning to pickup pulp-container after 2.19 assuming it releases not too close to Katello 4.13 branching
  • core/3.49
  • May upgrade to container/2.20 if we can
  • Check in with pulp_rpm at the same time - there may be a new release that can be grabbed as well
• Plan has begun for integrating with new container manifest labels et. al.

QE

• Sat-Next/stream : everything VERIFIED!
  • Cheering happened

[ggainey]

2024-04-03

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Released core/3.50 (and a lot of Zs) last week
• RPM
  • Released rpm/3.25.2
    • Includes repo_config gpgcheck value lost ? (mirror_complete option) · Issue #3462 · pulp/pulp_rpm · GitHub
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Good discussions w/ ATIX/pulp_deb
• When is the next pulp_container happening?
  • Iballou to ping lmjachky directly
• Upgrades looking good so far
• Query RE “protected repo version” : Github PR ?
  • Can we add a force/cascade flag?
  • Pro: Hard to get from repo-versions to have-distributions for some plugins
  • Con: Distribution is not hard-linked to repo-version
  • Suggestion: can we add an API to make it easier to go from “list of repo-versions” to “distributions pointing to them”
  • Observation: current error-msg doesn’t give us any help
  • AI: sjha to open an RFE - let’s move discussion there

[ggainey]

2024-04-17

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.51 released
  • Gunicorn fun NVD - CVE-2024-1135
    • Updated gunicorn-UB, backports released for core/3.22-28-39-49-51
• RPM
  • Nothing upstream should be affecting katello
    • Fix modulemd defaults upload by pedro-psb · Pull Request #3503 · pulp/pulp_rpm · GitHub
    • Might need backporting for upstream user
• Ansible
• Pulp Container
  • Still waiting for container/2.19 for katello
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Core-upgrade is going well
  • Waiting for releases to be RPM-d
  • Should have 3.49 branch soon
  • Looking into capsule-sync issues - may not be Pulp
• Container-push questions
  • Talk to lmjachky

QE

• Sat-Current BZs looking good
• Current testing looks good for Pulp
• Artifact-to-file linkage question

[ggainey]

2024-05-01

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.53 and 3.49.6 released
  • Q: recent pulp-container NFS benchmarks
    • New perf-test, or just reporting what Pulp team discovered?
    • Unsure - but probably based on Pulp numbers
• RPM
  • RE Performance
    • RHEL repos grow over time so can affect numbers
    • Some discussion ensued
• Ansible
• Pulp Container
  • Upgrade issue - v1-manifest-support bit us unexpectedly
    • Needed a katello fix
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• QE will be picking up container-push testing “soon”
• Sat-6.15 release may result in new issues (due to Actual Users)
• Sat-next testing starting
• Discussion RE Jira transition
  • Slack integration exists - talk to iballou!

[ggainey]

2024-05-15

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Issue involving large exports (and imports) discovered (katello-4.12/core-3.39)
    • Export of large amount of packages will result in errors · Issue #5375 · pulp/pulpcore · GitHub
• RPM
  • Release this week or next week (rpm/3.26)
• Ansible
• Pulp Container
  • Released 2.20 with artifactless manifests (Changelog — Pulp container Support 2.21.0.dev documentation)
    • Shipping an updated django-management command to handle the migration of both labels/annotations and manifests
    • Already accepted/merged into katello
• OSTree
• Pulp CLI
• Pulp Replica
• Mtg 29-MAY - ggainey on PTO
  • Iballou to run the mtg

Katello

• Pulp-related feature dev is “all going fine”
  • On-track for Sat-Next features!
• RFE for filtering on manifests/labels? (pulp-container)
  • Maybe for next release?
• Foreman-birthday-party in DE coming
  • Foreman Birthday Event 2024 - Celebrate the 15th birthday - Events - TheForeman
  • Would be cool if anyone form Pulp could attend

QE

• Not much to report
• label/annotation testing of manifests starting next week
  • Expect incoming pings from QE

[ggainey]

2024-06-12

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.55 to be released #soon (next Tues?)
  • Next breaking-change for core will be 3.70
  • Working on how Jira integration will work w/ pulp’s process
• RPM

  • hyu@ addressed another advisory-merge-edge-case (#3587)

  • Publishing checksums - SHA1 Fun in katello

    • Katello addressed the issue
    • Katello now off of SHA1 and also removed deprecated functionality
• Ansible
• Pulp Container
  • As a user I want to mirror container manifests by digests · Issue #1563 · pulp/pulp_container · GitHub (revisiting sync by digest; compatibility with OSP and Satellite for existing customers)
    • Need to hear from PM about what/where/when/how - who should we be nagging?
• OSTree
• Pulp CLI
  • Reverted allowing requests-2.32 due to https regressions
• Pulp Replica
• Virtual PulpCon will be happening in November-ish
• Possible in-person team mtg - location/feasibility tbd
  • Sync up w/ local katello/foreman/qe folk?
• Bindings-generation-discussion continues apace in discourse
  • Current decision: not going to do this “now”
  • won’t block core/3.55
  • Isn’t a “breaking change” in the context of the plugin-api - so doesn’t really need to wait on a core-breaking-change release
  • Lots of discussion still to be had in discourse thread

Katello

• Container push support nearing completion
  • Under “heavy testing”, yay!
• Next up: upgrading to rpm/3.26

QE

• Verifications for Sat-Next are in-train

[ggainey]

2024-06-26

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.55 released
    • Plugin-compat-releases are largely available
    • The release train left the station! 3.55 and other new versions of Pulpcore are comming to town!
• RPM
  • Once it’s locked in that Satellite-Next will use pulp_rpm 3.26, let me know so I can update the supported versions list accordingly
    • Esp important since rpm/3.27 is out
• Ansible
• Pulp Container
  • Downstream supposedly wants us to start working on As a user I want to mirror container manifests by digests · Issue #1563 · pulp/pulp_container · GitHub (manifest sync by digest). Is there any deadline for it?
    • We need input from roadmap/product-planning Soon
    • FWIW, pulp-team has escalated from our side
• OSTree
• Pulp CLI
• Pulp Replica
• Discussion around Pulp no longer building bindings continues
  • See latest addition for discovering one of the expected problems “in the wild”

Katello

• Repo creation errors out with Ruby bindings · Issue #3639 · pulp/pulp_rpm · GitHub
  • Blocking RPM 3.27 upgrade
  • I’d offer to regenerate the bindings myself but we’d need to upload them somewhere, and they’ll likely get overwritten by the next z-stream upgrade of pulp-rpm.
  • Collides with delivery-pipeline process
  • Can we get some more problem-determination from the Ruby side?
• Katello would like to be on more-recent-rpm if possible

QE

• Sat-Current verifications in progress, no blockers AFAIK
• Some discussion about/around automating testing a scenario that requires a HUGE amount of data - prob will end up in performance-test-harness