Katello/Pulp3 Integration meeting

[ggainey]

November 16, 2022 (9-NOV skipped for PulpCON)

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • 3.22 currently slated for 30-NOV
    • Will include domains (multi-tenancy)
• RPM
  • Domains-in-rpm planning started
  • BZs in progress
• Migration
  • 0.11.3 released for last 6.9.10 zstream
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
  • 0.16 released
  • CHANGELOG

Katello

• Conflicting Meetings make moderators Sad

QE

• “Fun” simultaneity BZ logged (poss a dup?)
  • Oh look - shared-distttree-subrepo problem
    • 2142689 – Capsule sync fails when a CV is published and promoted to two capsule's LCEs at the same time
    • 2103246 – Capsule sync fails with duplicate key value violates unique constraint "core_repositoryversion_repository_id_number
  • Already in main and rpm/3.18
  • Backporting to rpm/3.17 requires a diff patch - need advance warning

[ggainey]

November 30, 2022

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • 3.22 release tentatively scheduled for 5-DEC
• RPM
  • More progress on dropping the libmodulemd dependency
  • Lots of BZs being escalated by support, trying to investigate
  • ppicka will be leaving RH, RPM Team somewhat undercapacity for a bit
• Migration
• Ansible
• Pulp Container
• OSTree
• Pulp CLI

Katello

• Pulpcore 3.18 branch upgraded pulp-rpm to 3.18.9 (From 3.18.7)
  • Client bindings are also at 3.18.9
• Escalation around “container-stuff on smart-proxies”
  • https://bugzilla.redhat.com/show_bug.cgi?id=2148813
  • Entirely fixable on katello-side, woo!

QE

• verified 1948930 – Discrepancy in the packages count in a repository on the client and Satellite
  • so many NEEDINFOs - ggainey to investigate/clear
• Will wait for build-team for downstream packaging of fix for https://bugzilla.redhat.com/show_bug.cgi?id=2148813

Build Team

November 23, 2022

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • Pulpcore 3.22.0 scheduled for Nov 30, but will likely slip by one week
    • All tests converted to Pytest and build team should be able to run them on the RPMs they build.
• RPM
  • Considering allowing users to skip treeinfo file. How is katello using the skip types?
• Migration
• Ansible
• Pulp Container
• OSTree
• Pulp CLI

Katello

• Pulp_deb monkey patch in the works. Should make it to 4.7 GA.

[ggainey]

December 7, 2022

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • 3.22 will be going out next week
• RPM
  • Primarily working on escalated BZs
  • Fedora discussions around XML-modulemd are finishing up
    • [Modularity] XML format for in-repository modules - devel - Fedora Mailing-Lists
• Ansible
  • 0.16.0 is out: Changelog — Pulp Ansible 0.17.0.dev documentation
    • Deprecated V2 and /ansible/collections/ upload endpoints
    • Renamed CollectionVersion upload fields [namespace, name, version] to expected_[namespace, name, version]
• Pulp Container
• OSTree
• Pulp CLI

Katello

• Bug #35829: Mirror complete sync policy no longer allowed with ignored content types in the repo. - Katello - Foreman → https://github.com/pulp/pulp_rpm/issues/2293
  • Katello fix will be released for 4.6 and 4.7

QE

• Question RE reproducing prob involving Azure
  • “Can’t sync from repo-in-azure.cr.io registry”
  • Hard to test fix w/out azure-access
  • 2026151 – Can't sync private Azure registry to Satellite
• Discussion RE deadlock-testing

[ggainey]

(NOTE: this meeting will be held next on 11-JAN-2023! Happy New Year, everyone!)

December 14, 2022

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • core/3.22 discussions
    • go/nogo tomorrow
    • May not contain the domains work?
  • Merged two PRs that that revealed unexpected plugin impacts
    • Labels-as-hstore (addresses user-reported performance issue w/ labels)
      • Fixes in progress
    • content-app redirects (BZ 2104792)
      • Being reverted for now, to be revisited post-3.22
  • Incremental filesystem import/export
    • Not implemented yet
    • Causing support heartaches
• RPM
  • 2 BZs nearing resolution
    • Dup-advisory
    • modulemd-multiple-get
  • Pulp_rpm is mostly ggainey and dalley
• Ansible
• Pulp Container
  • Fix maxing out idle db connections on pulp_container 2.8.x
    • https://github.com/pulp/pulp_container/pull/1176
  • 2.8.9 will be released soon
• OSTree
• Pulp CLI
• No meeting 21/28-DEC or 04-JAN-2023
  • ggainey to cancel invites

Katello

• Bug #35829: Mirror complete sync policy no longer allowed with ignored content types in the repo. - Katello - Foreman → https://github.com/pulp/pulp_rpm/issues/2293 made it to 4.7 and will be part of 4.6.2
• 6.12 upgrade issue
  • Katello db somehow allowed ‘errata’ into “ignore types”

QE

• testing deadlock BZ - reproducible in 6.12.0 with rhscl, NOT reproducible in 6.12.1 with bigger rhel7 repo (5 CVs, on_demand on SAT side, immediate on CAPS side) - so far looks good!

[ggainey]

2023-01-11

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • core/3.22 released, 3.22.1 Real Soon Now to fix a migration issue
  • Should katello-next update to 3.22?
    • Leaning towards “no”, depends on features
    • When does katello need to make a call?
  • A couple backports went out yesterday for various BZs
    • core/3.18 and core/3.21 updated
• RPM
  • Modulemd is proposing to add/be-changed-to .xml (instead of yaml) - does anything in katello (applicability?) look at the modulemd yaml directly?
    • Nope! I didn’t even know we had access to that. [Ian]
  • RHEL moving forwards with a change to stop shipping un-compressed comps.xml
    • Or maybe not. We’re talking through some issues with the DNF team
    • May impact which pulp versions support future versions of RHEL 9.Y
    • We can/will do backports if necessary
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Meeting Review
  • Is this useful?
  • Is the cadence useful?
  • Is the format useful?
  • Is the invite-list correct?
  • Is “katello issues” link above useful at all? (suspect not)
    • Current query not relevant
    • No current equivalent
  • Think about these questions, decisions next week

Katello

• katello/4.8 branch - when?
  • Tentatively “early Feb”
• Discuss incremental export
  • 2143497 – Can't perform incremental content exports in syncable format
  • Paji to schedule a meeting with dalley/ggainey
• Pulp-replica project?

QE

• No updates
• BZ-verification underway for next-Y and next-Z

Build Team

[ggainey]

2023-01-18

Overview

• Katello Schedule

Pulp

• Meeting Review
  • Is this useful?
    • Does Ansible need to actually be here?
    • Maybe just add report to the doc prior to the mtg
  • Is the cadence useful?
    • Seems to be
  • Is the format useful?
  • Is the invite-list correct?
    • Corrected with input
• Pulpcore
  • Query of all changes from last week
  • Pulp-replica project update?
    • Basic CLI POC in progress
    • “Replicate” starts with repo/distribution on src-pulp, creates remote on downstream-pulp to create/sync/publish/distribute in downstream
    • Experimentation in progres - talk to dkliban to learn/get involved
    • Pulp Replication - HackMD
  • Requesting feedback on “How do you view ‘tech preview’?” discussion
• RPM
  • Scheduling a discussion about possibly restructuring the incremental update features to be more foolproof, possibly eliminate depsolving
    • RHEL8, libsolv, and module Sadness
• Ansible
• Pulp Container
• OSTree
• Pulp CLI

Katello

• Duplicate data with unique indices: 2142270 – Locale change caused by RHEL upgrade results in database index corruption "get() returned more than one Modulemd -- it returned 2!"
• Discuss https://github.com/pulp/pulpcore/pull/3511/

QE

[ggainey]

2023-01-25

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • Pulpcore 3.22 requires hstore module for postgresql. The installer needs to account for this.
    • Requires superuser to install pre-postgres13
    • investigation/discussion in progress, please give input!
      • Iballou to collab w/ dkliban
      • File a ticket here: https://projects.theforeman.org/projects/puppet-foreman/issues/new
    • Katello-evr-install already tread this ground
      • Delivery via RPM should address
      • What about capsules?
    • https://github.com/pulp/pulpcore/issues/3400 ← issue that caused this change
• RPM
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
  • https://github.com/dkliban/pulp-replica
  • This is a new plugin that will be used to provide an API for replicating an upstream Pulp to a downstream Pulp.
  • Currently supports File and RPM plugins. Just the happy path.

Katello

• 2162591 – Oracle JDK rpms no longer work
• Upcoming CDN changes that block crawling – any updates needed?
  • Will Pulp also change to block crawling for protected repositories?
    • pulp doesn’t do index.htmls, either to sync or as part of its repos - unaffected

[ggainey]

2023-02-1

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • Django-reqt-changes to match django security releases (3.2.17 just released)
  • Discussion on https://github.com/pulp/pulpcore/pull/3511
• RPM
  • Monday: meeting to discuss dependency solving issues and future
  • Dalley action items:
    • Need to hunt down HCaaS use case investigation data re: incremental update
    • Tying up all of the “RPM name” issues / BZs
  • Zstd compressed metadata support probably being added soon
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Pulpcore 3.22 upgrade likely pushed off to Katello 4.9
  • Installer change: https://github.com/theforeman/puppet-pulpcore/pull/275
  • Python-crypto has a Rust dependency, and the Build Gang has a Sad

QE

• 6.12.2 BZs verification
• 6.11 → 6.12 upgrade - pulpcore migration fail - is it familiar to anyone?
  • “AttributeError: ‘Settings’ object has no attribute ‘CONTENT_ORIGIN’"
    • If CONTENT_ORIGIN isn’t set, your Satellite isn’t installed correctly
  • Try “sudo -u pulp PULP_SETTINGS=’/etc/pulp/settings.py’ /usr/bin/pulpcore-manager migrate”

[ggainey]

2023-02-08

Overview

• Katello Schedule

Pulp

• Lots of folk prepping for/travelling to/at FOSDEM and CfgMgtCamp
• Pulpcore
  • Query of all changes from last week
  • Fsexporter-incremental merged, backported to 3.22 and 3.21
  • Discussions around backporting deadlock-fix to core/3.14 in progress
• RPM
  • Tying up all of the “RPM name” issues / BZs
    • There’s 2 more now than there was earlier, so now trying to tie those together as well
    • ~4 BZs, 1 other customer case, ~2 upstream issues
    • At this point resolving all the confusion is collectively a high priority
    • Biggest problem is that there’s some overlap with a perennially very difficult issue, “relative path problem” which may require architectural adjustments to come to a solution that makes everyone happy
    • On the bright side it might be more addressable now than it once was
  • 3.19 released
    • Includes RBAC support
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Looking less likely that we’ll move to Pulpcore 3.22 for katello/4.8
  • Build Gang may be making progress? Iballou to check
  • Maybe start thinking about doing a core/3.xx upgrade in the katello/4.9 branch
• An rpm-name-issue reproducer can be found 2162591 – Oracle JDK rpms no longer work
  • Difference between katello and hammer uploads?

QE

• Expect questions from QE next week to Pulp on testing

[ggainey]

2023-02-15

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • Deadlock fix backported to 3.14 and released
  • What if core movies to calendar versioning?
    • Switching Pulpcore to Calendar Versioning scheme - #7 by ggainey
• RPM
  • Some work going on upstream about package signature verification
  • Worked with Vladimir on https://bugzilla.redhat.com/show_bug.cgi?id=2122872
    • Seems like there’s still a problem? But it makes no sense
    • Does Katello start indexing immediately during or after a sync?
      • [ian] Katello indexes after the sync is complete
    • Should we institute restart-gunicorn-processes-regularly to “stop the bleeding” while we try and figure out what’s going on?
    • An upstream user may be experiencing this problem as well, Pulp will ping to get them to open an issue
    • Dralley to comment on BZ RE “this shouldn’t block a release”
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
  • Splitting pulp-cli into pulp-cli and pulp-glue
    • Needed for several incoming projects
    • Build Gang implications?
• Pulp Replica
  • Moved the code into pulpcore. Still should be available with 3.23.
    • Enables replicating distributions/repositories from another Pulp. by dkliban · Pull Request #3568 · pulp/pulpcore · GitHub
    • Need a working-group RE “how can we implement this into foreman/katello?”
• When should we hold this meeting?
  • Colliding w/ previous-slot katello mtg
  • Plan to discuss next week

Katello

• 2160008 – (Regression of 2033940) Error: AttributeError: 'NoneType' object has no attribute 'cast' thrown while listing repository versions
  • Back-portable to Pulpcore 3.18.12 safely? Are extra commits required?
    • It’s already in 3.18.13 and it’s the only patch in that release?
    • Patchback applied cleanly, should be good to go
• katello/4.8 moving to core/3.22!
  • Already built!
• DevConfUS happening in Aug in Boston, CFP is out
  • Does Pulp want to send anyone?
  • Katello will have a booth

QE

• gunicorn mem BZ failed 2122872 – pulpcore-api gunicorn process consumes high memory
  • 6.11 didn’t seem to have the issue?
  • Maybe work w/ wclark to see what options we can give for mitigation

[ggainey]

2023-02-22

Overview

• Katello Schedule

Pulp

• Pulpcore

  • Query of all changes from last week
  • Fix for 3075 backported to 3.16 and 3.18 branches
    • Do we need a release to get the fix into customer hands?

• RPM

• Ansible

• Pulp Container

• OSTree

• Pulp CLI

  • pulp-cli/pulp-glue split caused some Fun Times in CI

• Pulp Replica

• When should we hold this meeting?

  • [ian] Katello is moving the prior meeting back 15 minutes.
  • [ggainey] cheers wildly

Katello

QE

Build Team

[ggainey]

2023-03-01

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
• RPM
  • Fixed https://github.com/pulp/pulp_rpm/issues/2961
    • Backported to 3.19
  • Improving end-to-end metadata integrity tests
  • Have not been able to reproduce the module API appearance differences yet? Tried with 3.17, 3.19, 3.17 → 3.19
    • Array-of-strings vs JSON
    • Iballou modified katello to handle both scenarios
  • Lots of new BZs incoming
    • Help prioritizing?
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
  • Merging into pulpcore “really soon” (for core/3.23)
  • Needs some plugin support as well
  • Needs content-protection before integration w/ katello
  • Discussion: what about ACS?
    • It works to the degree that ACS is set up ‘downstream’

Katello

• Dep-solving discussions - prob needs some resolution
  • Small incremental improvements in workflow/docs
  • Needs an epic for katello/4.9

QE

Build Team

[ggainey]

2023-03-08

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last week
  • Ggainey will be reporting for core
    • Dkliban out on paternity lv until 5-JUN
  • core/3.23 to happen #realsoonnow
    • Poss this/early next week
  • Pulpcore future versioning plans
    • core/3.25 to be linked with Django-4 upgrade
      • Poss in April/May-ish timeframe
    • Pulpcore versioning to happen MUCH more rapidly post-core/3.25
    • See thread Switching Pulpcore to Calendar Versioning scheme - #12 by ggainey
• RPM
  • BZ work continues
    • 2170535 – Yet another deadlock during Capsule sync, now when existing content changed (deadlock)
  • Rocky-linux-sync Fun
  • Dkliban PR for pulp-replication Stuff
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
  • Release coming #soon - mostly w/ domain support
• Pulp Replica
  • Will be in core/3.23
  • Rpm-support-pr is opened
• Review meeting cadence
  • can/should we move to every-other-week?
  • Sjha - maybe try every-other. Meeting is useful
  • Dralley, vsedmik - +1
  • Add new QE rep (sweta)
  • AI: ggainey to move this to every-other-week as an experiment

Katello

• Starting to test out pulp replica w.r.to POP and smart proxy use cases.
  • Sjha has a card
• Domain work is also exciting - yay!
• How big of a no-no is a flag on a repository telling us if repo has been synced with immediate and bits exist on filesystem?
  • More specifically - knowing that all content-artifacts exist on disk
• “How much disk space is being taken up by a repository”
  • The perennial question
  • Dralley has a tool for rpm-repos that “sort of” answers this
  • COPR support may want something similar
  • “Its Very Complicated”
    • Artifacts are deduplicated
    • Metadata takes space
    • Postgres takes space
    • On-demand doesn’t take space (but could)
    • Deduplicating filesystems make things even more interesting

QE

• No major updates
  • Lots of BZ work (compressed comps file)

[ggainey]

2023-03-22

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.23 file/1.13 and certguard/1.6 released
    • Domain support
    • We need to fix some lowerbounds - will be .1 releases Soon
  • Gonna stop publishing nightlies to pypi - is that ok?
    • What about rubygem nightlies?
    • AI: ggainey to inform team “yes we can stop doing that”
• RPM
  • In the process of fixing the API in 3.19, encountered some issues with module depsolving. Seems to have been broken for a while.
    • I’ll try to put the test up at least, but nobody has complained so far, so it’s not a high priority
  • Working on PR to fix modulmd-packages-import-export being broken
    • Hyu has a great PR, will be backporting the fix
    • BZ 2178176 – Satellite showing errata from module streams not installed on client as upgradable/installable when content is imported (not synced)
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica
  • PRs in progress for file and rpm

Katello

• Looks like 4.8 should be out “soon”, is that correct? Yes. Nightlies are green and so is 4.8 after pulp_rpm 3.19.2. We have an action item to re-record our VCRs assuming format of data returned is changed.
  • Does katello turn on pulp-analytics in the upstream? - No
  • Still opt-in on installer
• Working on refining epics for Next-Y
  • Doesn’t look like many Pulp impacts (yet)
• katello/4.8 looks to be unblocked now, woohoo!

QE

• no updates at all - all ON_QA 6.13 BZs have been resolved

[ggainey]

2023-04-05

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Release
    • core/3.21.6 and 3.18.16
    • file/1.14
• RPM
  • Bugfix for import/export of modulemds
  • Bugfix for uploaded package 404 issue
    • Dalley working on tool to fix already-existing problems
  • 2122872 – pulpcore-api gunicorn process consumes high memory next on prio list
  • rpm/3.20 coming #soon
    • Domain-support and an RFE (restrict acceptable pkg-signing-keys for a repo)
• Ansible
• Pulp Container
  • container/2.14.4
• OSTree
  • Had its first GA release
• Pulp CLI
• Pulp Replica

Katello

• 2155644 – When importing the content in a disconnected satellite, the customer is facing "Error: 502 Bad Gateway"
  • OOM issue with import? Curious if you think there could be an improvement.
  • Import-time fix : 2170485 – Importing Red Hat Repository Import on Disconnected Red Hat Satellite taking huge time around 5 hours (not released yet?)
  • Memory-fix: 2061224 – MemoryError when importing large repo to disconnected Satellite
    • Released last year : Red Hat Customer Portal - Access to 24x7 support and knowledge
• What happens to the contents on disk if a content import fails? Do they stick around?
  • If so, where? And when will Pulp clean it up?
    • There is suspicion that these files stay in the cache. Reportedly there were times when, after a failed import, the next import would require more storage space than the last.
  • Possibly depends on exactly what fails when - need data please
  • Pulp does not touch/erase the import-files themselves
• Sync-up on https://issues.redhat.com/browse/SAT-16225
  • Tips for collecting data about whether or not incremental-update needs dependency solving?
    • Discussion around breaking-scenarios
    • Dalley’s tool can find “rpms not ‘covered’ by errata”
      • Provide timestamp-per-repo of release-timestamp, repo-urls
  • Docs draft will be written by us devs and then passed on to the documentation team
  • Is this an ask for the Pulp team to take on this task? Because if so, that’s new.
    • Nope!
    • Pulp to collaborate on review
• 2174912 – [RFE] add ability to skip syncing .treeinfo files (skip .treeinfo)
  • “Pulp side” released in rpm/3.18 and 3.19 already
  • See 2046195 – Katello::Errors::Pulp3Error: Treeinfo file should have INI format for the original “Broken upstream” error traceback

QE

• Shweta picked up incremental-export-sync after switching from on_demand-to-immediate

[ggainey]

2023-04-19

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Bugfix releases
  • What does katello think about accepting performance-improvements for which there are not currently BZs?
    • https://github.com/pulp/pulpcore/issues/3711
    • https://github.com/pulp/pulpcore/issues/3714
    • Discussion ensued
      • If upstream would like it backported, go for it
      • If Pulp wants QE’s help to test a thing, it must have a BZ and follow the process
• RPM
  • Bugfix releases
  • Memory-use in gunicorn investigation continues 2122872 – pulpcore-api gunicorn process consumes high memory
  • Pulp_rpm domain work continues
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
  • 0.19.0 released
• Pulp Replica

Katello

• Any upgrade wishes for the next few Katello releases?
  • core/3.23 has domain work
  • core/3.25 will have django4
  • katello/4.9 branching in “a month”, core/3.22
  • Maybe katello/4.10 will aim for core/3.25(ish)

QE

• One BZ pending for z-stream
  • 2184122 – wrong metadata if uploaded rpm have different name than name in rpm

[ggainey]

[missed posting previous minutes]

2023-05-03

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.24 released
    • Having Some Issues, will update
  • core/3.25 is coming #soon (May-ish)
    • Moves to Django4.2, psycopg3
    • katello/4.Next should prob think about being core/3.25 or later
• RPM
  • Fix for the profiles issue that Ian reported on Slack is ongoing
  • 3.20 release today
    • No domains yet, alas
• Ansible
• Pulp Container
  • Plugin leadership change, goes to Lubos!
  • Ggainey will add him to invite
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Core-repair API will be in-use for capsules
  • Nudge lmjachky about container-issues involving repair
    • This is a core issue https://github.com/pulp/pulpcore/issues/3606
  • Katello will need fixes “soon”
    • Added prio-list label on repair related issues
  • Thoughts about large/manyrepo/huge-dataset systems - per-repo, or global-repair?
  • Discussion needs to happen! Poke lmjachky?

QE

• Nothing to yell about
• Sat6.13 released today!
  • And there was much rejoicing

[ggainey]

2023-05-17

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • core/3.26 released
  • OpenTelemetry basic support merging into pulpcore
    • Will be available for use by perf-test
• RPM
  • 3.17.18 released
  • 3.21.0 release soon
    • Mostly domains, core/3.25 required
• Ansible
• Pulp Container
  • Podman-push-repo-versioning is changing
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• 2142689 – Capsule sync fails when a CV is published and promoted to two capsule's LCEs at the same time
  • Capsule-sync-race-condition?
  • Needs more eyes, from both sides (pulp/katello)
• 2077363 – Fail to sync kickstart repositories with same sub repositories concurrently hotfix requested for Sat 6.11
  • 3.17.18 released with this fix
• How could 2174912 – [RFE] add ability to skip syncing .treeinfo files be given an automated test?
  • It seems it’s not the repo, but the web server that causes the original bug?
  • Idea: test .treeinfo file existence
  • Dalley: just test sync with / without treeinfo skipped and whether it downloads the .treeinfo. As you say, this just just a way of working around webserver problems, we don’t need to test the webserver.
    • We already have an upstream test for this Added 'treeinfo' to available skip-types at sync time. by ggainey · Pull Request #2913 · pulp/pulp_rpm · GitHub
    • I doubt it’s worth writing a 2nd automated test
• Working with OpenStack team on https://issues.redhat.com/browse/RHOSINFRA-4958
  • They’re having potential issues with Satellite & container content – may be just a usage issue but just FYI.
  • Let’s make sure lmjachky has access to test systems to help

QE

Build Team

• core/3.25 and Django4 is coming - heads up!

[ggainey]

2023-05-31

Overview

• Katello Schedule

Pulp

• Pulpcore

  • Query of all changes from last two weeks
    • OpenTelemetry initial support now baked in
  • 3.27 and a lot of X-releases this week
    • Release Day! May 30, 2023: Pulpcore 3.27 and more
  • core/3.25+ OCI images now available
  • Memory use investigation has made progress. Querying and Serializing the changelogs is pretty much the culprit.
    • Workarounds suggested, issues filed
    • https://github.com/theforeman/puppet-pulpcore/issues/286
    • https://github.com/theforeman/puppet-pulpcore/issues/285
    • Will be/is in latest foreman release
  • Potential fix for 2188504 – The "hammer export" command using single thread encryption causes a performance bottleneck. (export-compression and performance)
    • Note for us: if we want to propose API-lvl changes, we can “just open a Jira” for katello and all The Right People will be informed automagically
  • Rerun-chunked-import fix for 2173757 – Can't rerun a failed content-import task if it was exported using chunks under review

• RPM

• Ansible

• Pulp Container

  • 2.15 release compatible with pulpcore 3.25, django 4.2

• OSTree

• Pulp CLI

• Pulp Replica

Katello

• Katello/4.9 release in progress
• https://issues.redhat.com/browse/SAT-16055

QE

• Sat-next Snap1 is out, no pulp issues yet

[ggainey]

2023-06-14

Overview

• Katello Schedule

Pulp

• Pulpcore
  • Query of all changes from last two weeks
  • Import-rerun merged, backported, released (3.18/21/22)
  • Release Day happened : Release Day! June 14, 2023: Pulpcore 3.28 and more
  • import/export-compression-fix also merged/released
• RPM
  • deadlock fix released, backported to rpm/3.17-18-19-21-22
    • https://github.com/pulp/pulp_rpm/pull/3002
• Ansible
• Pulp Container
• OSTree
• Pulp CLI
• Pulp Replica

Katello

• Does pulp have native backup/restore?
• 2151333 – Mirror complete sync policy no longer allowed with ignored content types in the repo.
• https://issues.redhat.com/browse/SAT-16330 Repair API - Docker content updates if any?
  • Is this https://github.com/pulp/pulpcore/issues/3606 ?
    • Yes, needs to be fixed “soon” (altho mayhap not ASAP)
  • See also 2127537 – [RFE] If an artifact gone missing from filesystem for any reason there is no way to easily redownload the same in Capsule 6.12
• Discussion RE katello/4.10 and core-release
  • Let’s try to get “further up” than core/3.25
  • Ian to look over the changelogs to see if core/3.28 would be good

QE

• Gunicorn “fix”?
  • Cfg-change to auto-restart workers “regularly” (not a pulp-change, a foreman-installer change)