---
# System prepended metadata

title: 'Pulpcore/katello/pulp_deb integration meeting, 2025 archive'

---

# Pulpcore/katello/pulp_deb integration meeting, 2025 archive

##  2025-12-02 1000-1030 GMT-5
### Attendees: 
### Regrets:
### Agenda:
* Who has permissions to close https://projects.theforeman.org/issues/37708 (as a duplicate of https://projects.theforeman.org/issues/38061)?
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-11-04 1000-1030 GMT-5
### Attendees: sjha, iballou, hhstct, pbrochado 
### Regrets: quba42, ggainey, vsedmik
### Agenda:
* quba42: Regarding client generation for Katello, we do this for the downstream: https://community.theforeman.org/t/we-finally-got-unlucky-with-the-generated-pulp-bindings/44812/5?u=quba42
    * Possible PulpCon showcase and discussion session?
    * Ideas of creating a independent ruby version of pulp-glue
* quba42: Structured APT is now merged for Katello 4.19. This means that this long saga of a story is now moving inextricably towards that final phase of the software lifecycle: Longterm maintenance. Thanks to everyone involved for making this happen!
    * I have started writing upgrade docs here: https://github.com/theforeman/foreman-documentation/pull/4452
    * There is also a related general docs PR here: https://github.com/theforeman/foreman-documentation/pull/4215
    * Katello 4.19 branching appears to be scheduled for 2025-11-11: https://community.theforeman.org/t/katello-4-19-branching-process/44803
    * [Ian] we should add a release note to 4.19: https://hackmd.io/LqYCeghBSpSmD1nkQQ-Mhw
* ACS for deb is merged on the pulp_deb side, and being worked on for Katello.
    * We may open a PR against pulpcore, because we want the ACS feature for pulp_deb without the `paths` feature (because we think it does not make sense in APT repo world/will cause more user confusion than user value here). For now we are inheriting the `paths` API parameter, but added validation that prevents users from trying to use it. This means we can move the feature along while coming up with a more permenant/better solution.
* katello updates
    * trying to get rid of old angular code
    * trying new feature for image-mode for showing transient packages
* pulp AI Policy: https://pulpproject.org/help/more/governance/ai_policy/

### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-10-07 1000-1030 GMT-5
### Attendees: ggainey, pbrochado, vsedmik, sjha, iballou, quba42
### Regrets:
### Agenda:
* Previous AIs:
  * Update on Incremental CV update performance?
  * Update on HTTPS proxy woes?
* quba42: I noticed there is still Pulp 2 stuff in the Katello code base. Is it safe to ignore/remove?
    * there exists [a PR](https://github.com/Katello/katello/pull/10721) to yank all that out
    * please tell iballou it's worth finishing :)
* [PulpCon 2025!](https://discourse.pulpproject.org/t/virtual-pulpcon-2025/2119)
* hstct: We are looking to enable ACS support for debian in Katello. Hoping for some pointers what to look out for :)
    * pulp_rpm acs initial support commit:
        * https://github.com/pulp/pulp_rpm/commit/0c9ee0e6d337eb50df90d50df9517045b57f2a82
        * some outdated stuff there
    * there exists a pulp_deb PR, but there's a lot in the way
* quba42: "Migrate all deb content to structured APT" (https://github.com/Katello/katello/pull/11487) nearly done.
    * What is the deadline for inclusion in Katello 4.19 (When does it branch?)
        * December-ish
    * Upgrade docs: I understand version specific upgrade docs are written after branching. How can I be "pinged" to provide those docs at the relevant point in time?
        * do docs and put them into nightly (will be carried into 4.19 branch automatically)
        * remove post-branching (if not needed after)
    * Regarding review: Has been reviewed and tested internally at ATIX. (And also released within orcharhino, i.e. "tested" in production; i.e. we are confident in the current state)
        * Essentially all changes are within `repository.deb?` type guards, so low likelyhood to impact other content types
        * One open thread regarding how talkative the migration task should be on systems that don't have any deb content
        * Expectation: resolve that thread, add two more tests, then merge by ATIX maintainer.
* Can/should we widen this to add other community contributors?
    * G-Research just added [Pulp Manager](https://github.com/pulp/Pulp-manager/)
    * consensus: The focus of this mtg is "people who need to coordinate between pulp **and katello**"
* iballou: does ATIX coordinate with EU OS?
    * https://eu-os.eu/
    * Jonas? met with iballou
    * maybe another contender for adding to this mtg
    * working w/ katello/foreman already

### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-09-02 1000-1030 GMT-5
### Attendees: pbrochad, Bernhard S, Jan B, Quirin, Samir, Tobias, Vladmir, ggainey
### Regrets:
### Agenda:
* Previous AIs:
    * update to py3.11 as minimum (py3.9 EOLs in October)
    * core<3.100 (should be done by the time this mtg happens)
    * both accomplished via [1311](https://github.com/pulp/pulp_deb/pull/1311)
* quba42: Thanks to everyone involved with rolling CVs! https://github.com/Katello/katello/pull/11407
* quba42, iballou: Rolling CV tests for robottelo
    * We added some to our internal robottelo set, should we move this upstream?
    * May be a bit complicated because of required internal fixtures
    * There are some PRs related to that opened, so there is some coverage. E.g:
        * https://github.com/SatelliteQE/robottelo/pull/19262
        * https://github.com/SatelliteQE/robottelo/pull/19277
* quba42, mbucher: Small open PR: https://github.com/Katello/katello/pull/11481
* quba42: Migrate all deb content to use structured APT for Katello 4.19?
    * Draft PR: https://github.com/Katello/katello/pull/11487
    * How sure can I be that "during upgrade rake tasks" will really be run in all cases?
        * check out [foreman-upgrade](https://github.com/theforeman/foreman_maintain/blob/master/definitions/scenarios/foreman_upgrade.rb) - this is the "preferred way" these days
    * Where can I add docs to recommend users enable structured APT BEFORE upgrading to Katello 4.19 (or whatever version this will land in?)
        * happens as part of the release-process - post-branch
        * https://docs.theforeman.org/3.16/Upgrading_Project/index-katello.html
* quba42: Incremental CV update (RHEL/rpm content with >100 repositories and at least one filter) => OOM death
    * 188G of RAM is not enough
    * Not exactly good practice but apparently there are "reasons to do things this way"
    * Incremental CV update to bring back a errata
    * Why should this be a performance killer?
        * Even if there are many repos presumably only one of them needs the errata packages/copy action?
        * Same for the filter? (Does the filter perhaps apply to every repo even if there are no relevant packages?)
    * dep-solve on or off?
        * because "on" will try to dep-solve against All The Things
        * the claim is "off"
    * what is the form of the exact filter being used?
        * how is the filter applied? (can be limited to single repo, but if not, is applied to all of them)
    * Any Thoughts?
        * check on depsolve flags
        * check on where filter is applied
        * who can ATIX talk to with questions on CV-Incr-Update path - sjha or iballou
* quba42: HTTP proxy with SSL inspection. Host can reach the repo, Pulp fails with "certificate verify failed: unable to get local issuer certificate". Worked with Katello 4.14/pulpcore 3.49, not working with Katello 4.16/pulpcore 3.63 (both Python 3.11). Any ideas?
    * can we add CA explicitly? will that help?


### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-08-05 1000-1030 GMT-5
### Attendees: quba42, sjha, mbucher, vsedmik, hstct, ggainey, pbrochado
### Regrets:
### Agenda:
* Previous AIs:
* mbucher: ready-for-(re)review https://github.com/Katello/katello/pull/11371
    * can we poke jlenz?
* quba42: ready-for-re-review: https://github.com/Katello/katello/pull/11433
    * approvals happened
    * Once merged, I can clean up rolling CV environments for final review: https://github.com/Katello/katello/pull/11407
        * discussion ensued - desire to get this "ready for review" and then merge post-katello-branch
* [3.85](https://discourse.pulpproject.org/t/attention-pulpcore-3-85-soon-coming-to-a-release-near-you/2080) is coming!
    * [blocker list](https://github.com/pulp/pulpcore/milestone/14)
    * discussion around py3.11 and LB and support and stuff

* postgresql size issue on capsules: 
    * https://issues.redhat.com/browse/SAT-36270
    * https://issues.redhat.com/browse/SAT-19863 
    * discussion around the whys, ensues
    * affected table-examples (may be private, sorry) : https://issues.redhat.com/browse/SAT-19863?focusedId=26530168&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26530168
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-07-01 1000-1030 GMT-5
### Attendees: ggainey, mbucher, qjames, quba42
### Regrets:
### Agenda:
* Previous AIs:
    * None
* quba42: Update on "rolling environments": https://github.com/Katello/katello/pull/11407
    * sync-to-proxy fix *almost* ready
    * needs more unit-tests to cover all the state-changes
    * quba42 will undraft and ping when he thinks it's ready
    * katello pushing hard towards 4.18 dev-freeze - be aware
* Q: ATIX customer issue w/ update-capsule-repository task "starts, task-finds-no-capsules, dynflow shows green and then 'eventually' foreman-task turns red"?!?
    * transient/not-reproduceable
    * have we seen this before? (alas, no)
    * no issue yet, just reported
* katello-dev-server on a Mac VM (aarch64)
    * everything works *except* pulpcore, because RPMs only avail for x86_64
    * Pulp team doesn't build RPMs, TheForeman Build Gang does
    * Can you point foreman/katello at an "external/containerized" Pulp?
    * discussion ensues
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-06-03 1000-1030 GMT-5
### Attendees: pbrochado, manisha, sjha, ggainey, mbucher, quba42, vsedmik, hstct
### Regrets:
### Agenda:
* Previous AIs:
    * ~~quba42: open a UX issue RE "green task that didn't actually DO anything is...confusing"~~
      * https://projects.theforeman.org/issues/38406
    * ~~quba42: update rolling-content-view/environments issue w/ discussion about approach being taken~~
        * https://community.theforeman.org/t/transparent-content-view-for-limiting-repository-access-in-katello/39389/34?u=quba42
    * ~~hstct: work w/ SUSE to fix their repo?~~
        * "as far as we're concerned, we fixed it" (full mirror works, for example)
    * ~~ggainey: extend mtg to remainder of 2025~~
* pulp_deb and domains
    * is there anything we can do to help get https://github.com/pulp/pulp_deb/pull/1262 completed?
    * hstct will reach out this week if/when/as help needed
* quba42: I have some thorny questions on https://github.com/Katello/katello/pull/11399#discussion_r2123663339
    * sjha/crog will look into the question and verify
* quba42: Thanks for the following reviews (in work or merged):
    * https://github.com/Katello/katello/pull/11387
    * https://github.com/Katello/katello/pull/11386
* quba42: Quick "Rolling CV environments" demo
    * Q: Can a rolling-cv be associated with **zero** Lifecycle Environments?
        * defaulting to Library is...suboptimal
    * discussion ensues
    * Q: on create
        * what UX to use to allow associating to Lifecycle Envs at the time?
        * do we know the Org we'll be creating into?
            * UI has a "current Org", API requires explicit org-choice
        * katello UX discussion ensues
* sajha: The "last" rolling CV bug: https://issues.redhat.com/browse/SAT-33407
* query RE v4
    * https://github.com/pulp/pulpcore/pull/6574
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-05-06 1000-1030 GMT-5
### Attendees: quba42, mbucher, hstct, sjha, ggainey, vsedmik
### Regrets:
### Agenda:
* Previous AIs:
* domain-izing pulp_deb
    * is there any chance this could happen in Q3?
        * https://github.com/pulp/pulp_deb/pull/1262
        * tests copied from pulp_rpm - mostly working, still need some tweaking
    * hstct *will* reach out if/when/as help needed
* [quba42] Lack of permissions for [`app/lib/actions/katello/content_view/capsule_sync.rb` ](https://github.com/Katello/katello/blob/master/app/lib/actions/katello/content_view/capsule_sync.rb) result in a green task that does not sync anything. This was hard to debug. How hard would it be to have tasks fail with something like "permission denied" or else write a log warning or similar?
    * non-admin-user ran into issues
        * missing 'manage-capsule-content'
    * can we have katello be more-obvious about this error condition?
    * task syncs "everything you're allowed to sync" - and when that's an empty-set, "do nothing" is green
    * consensus: suboptimal UX, let's get a katello issue open 
    * AI: quba42
* snap support in Katello in addition to flatpak. Any plans or ideas already?
    * katello? or does Pulp need to do anything beyond "generic container registry" support
    * pulp_container supports OCI images
        * snap has its own format
    * pulp_rpm example - some RPM repos require special Remotes (SUSE, ORA) - but the *repository* is "just an RPM repo"
    * katello working on cert-auth for container-content - will happen in katello
            * will rely on entitlement-certs subman generates
            * https://issues.redhat.com/browse/SAT-32491
* [quba42] Rolling content view environments
   * https://community.theforeman.org/t/transparent-content-view-for-limiting-repository-access-in-katello/39389/33
   * Also: https://projects.theforeman.org/issues/38285
   * working on implementing maximal "can do rolling content view to any arbitrary environment" approach - POC in progress
   * needs a katello issue
   * can we follow this newly-proposed process : https://community.theforeman.org/t/rfc-defining-an-rfc-template-which-includes-a-decision-section/42628 to record the decision above?
       * AI: quba42 to update
* https://community.theforeman.org/t/katello-throws-file-already-exists-on-publication/43161?u=hstct
    * SLES repo is having problems
    * repomd.xml references two updateinfo.xml files (?!?)
    * newer pulp_rpm "works" (maybe creatrepo_c update fixed it)
        * works-ish
    * should we go back to SUSE? - yes please
* can we get input from ATIX/katello on RBAC useage/needs/desires?
    * https://discourse.pulpproject.org/t/gathering-information-how-do-you-use-pulps-rbac/1974

### Action Items:
* quba42: open a UX issue RE "green task that didn't actually DO anything is...confusing"
* quba42: update rolling-content-view/environments issue w/ discussion about approach being taken
* hstct: work w/ SUSE to fix their repo?
* ggainey: extend mtg to remainder of 2025
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-04-01 1000-1030 GMT-5
### Attendees: mbucher, sjha, ggainey
### Regrets:
### Agenda:
* Previous AIs:
* We **do not do** "April Fools!" jokes in this meeting! :)
* pulp_deb and domains
    * https://pulpproject.org/pulpcore/docs/dev/learn/domains/domains_compatibility/?h=domain
    * is ATIX able to investigate/implement domains-in-pulp_deb?
    * [pulp_rpm PR](https://github.com/pulp/pulp_rpm/pull/3106) for this
    * AI: mbucher to bring this back to the ATIX team
* [m-bucher] container-image naming in katello revisited
    * see last mtg's discussion
    * katello's container-name-regex more permissive than Pulp's
    * Pulp's regex [is different than](https://github.com/Katello/katello/pull/11336#discussion_r1995999097) OCI's? - why?
    * [current katello-PR](https://github.com/Katello/katello/pull/11336) should fix immediate issue
        * it's OK if katello is stricter-than Pulp's regex
### Action Items:
* [mbucher] bring to larger ATIX team "when can pulp_deb be taught about domains"
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-03-04 1000-1030 GMT-5
### Attendees: ggainey, vsedmik, qjames, quba42, mbucher, hstct
### Regrets: iballou
### Agenda:
* Previous AIs:
* [m-bucher]: Katello; Org with trailing `.` (e.g. `ACME Inc.`) => `{"base_path":["The provided base path contains forbidden characters."]}`
    * container-related - ORG with trailing-dot
    * Pulp is complaining, should katello sanitize?
    * is this container-only? pulp-content-app?
    * atix asking their support to experiment w/ deb/rpm
    * qjames: katello may have already fixed in 4.15-container-push
    * mbucher: will try against nightly
    * this *may* be specifically a not-legal-container-path Thing
    * *if* pulp is being "overly restrictive" around base-path-legality, we'll need an issue to get that addressed
    * **result:** Katello is not restrictive enough. https://projects.theforeman.org/issues/38269
      further dicussion needed on how to fix it!
* [quba42] Still open: https://github.com/candlepin/subscription-manager/pull/3454
    * ignored for 5 months?
    * let's try and get this reviewed/merged
    * ptoscano is prob a person to nag
* [quba42] Need packaging help: https://github.com/theforeman/foreman-packaging/pull/11793#issuecomment-2684243214
  (Known)Issue or already fixed?
    * skip for now - needs a complicated-packaging-dance to address
    * might happen as part of the ongoing katello-branch-and-rebase-to-new-pulp
* [quba42]: rolling CV: https://github.com/Katello/katello/pull/11240
    * Katello 4.16 has branched so we want to finalize ASAP.
    * Lots of review and rework activity happening.
    * Open issues:
        * Smart proxy sync not re-syncing rolling CVs in all cases (maybe fixed now)
        * Missing repo names for rolling CVs on the smart proxy view
        * Container push repos need to be disallowed
        * Why is `::Actions::Katello::ContentView::AddToEnvironment` async during rolling CV creation?
        * Hammer PR
        * docs PR
    * work is in-progress, will report if/when/as there may be roadblocks
    * PR might get taken over by mbucher
* Availabilty: quba42 on leave for 4 weeks starting next week, nag hstct for pulp_deb or mbucher for katello-deb issues
* [quba42] Potential future rolling CV extension: "I don't want to sync all of Library to smart proxy just to use my hand full of rolling CV repos"
     * Possibility 1: Call it something different for rolling CVs, e.g.: "RollingLibrary" or just "Rolling".
         * I don't want to introduce another new "special" name.
     * Possibility 2: Allow "promoting" rolling CVs to other LCENVs?
         * Easy enough to implement, but does not make a lot of semantic sense.
     * Possibility 3: Allow some kind of filtering by CV on the smart proxy sync?
         * Sounds hard and potentially disruptive.
     * Any other ideas?
     * qjames: let's rule out 1 above
     * qjames: 2 "makes more sense" (imnsho)
     * vsedmik: autosync-after-promotion
     * vsedmik: option 2 - breaks rolling-content-view "concept"
     * vsedmik: what about org-scoping libraries?
     * quba42: customers prob won't be happy w/ introduced complications of org-scoping
     * consensus: proposal-1 is Right Out. Discussion needs to continue
     * finish the existing PR, and then perhaps open the discussion to a wider audience
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-02-04 1000-1030 GMT-5
### Attendees: 
### Regrets:
### Agenda:
* Previous AIs:
    * ggainey to archive 2024 minutes
        * see [2024 minutes](https://hackmd.io/@pulp/pulp-deb-katello-integration_2024)
* [quba42] Is it intentional that a RH-manifest cannot be uploaded to two different organizations on the same instance? See: https://github.com/theforeman/foreman-documentation/issues/3585

### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

##  2025-01-07 1000-1030 GMT-5
### Attendees: sjha ggainey mbucher quba42 vsedmik hstct
### Regrets:
### Agenda:
* Previous AIs:
    * AI: ~~ggainey to schedule mtg-invite for next 6 months~~
* Conventions for how much review (ATIX and Katello team) different types of PRs need before they can be merged?
    * E.g.: Pure APT/deb type bugfix: https://github.com/Katello/katello/pull/11247
        * Requires pulp_deb domain knowledge
        * Style and naming convention review always welcome!
        * Is ATIX fix + ATIX review + ATIX merge acceptable in such cases?
    * discussion
        * sjha: generally, if separate-eyes reviewed and you have merge-rights - go for it
        * if you would *like* extra eyes - just nag somebody
* Rolling CVs:
    * Main PR "ready for review": https://github.com/Katello/katello/pull/11240
        * Depends on separate bugfix PR: https://github.com/Katello/katello/pull/11253
        * Hammer PR: https://github.com/Katello/hammer-cli-katello/pull/974
        * Docs PR: https://github.com/theforeman/foreman-documentation/pull/3518
    * discussion:
        * maybe not merge til after next-Y-branching happens
        * some small issues need to be addressed, but Almost Ready
        * want to be in "ready to merge post-branch" state "soon"
        * sjha: reviews may be delayed due to current crush of events
        * sjha: this/these PRs may need more attention from QE
        * vsedmik: assuming there's an RFE filed, will need test-coverage/person-assignment
            * is the RFE in the right "state" to be picked up by downstream process?
            * yes - it'll show up "soon"
        * quba42: will ping ppl if help needed

* Structured APT fixes:
  * https://github.com/Katello/katello/pull/11218 (merged)
  * https://github.com/Katello/katello/pull/11247
  * https://github.com/Katello/katello/pull/11259 (merged)
  * Start using: https://github.com/pulp/pulp_deb/pull/1168 (merged)

* 3.70 changes
    * [blocker milestone](https://github.com/pulp/pulpcore/milestone/13)
        * not releasing this week
    * "CONTENT_ORIGIN may not be set"
        * see [see this PR](https://github.com/pulp/pulpcore/pull/6175)
            * looks like pulp_deb
    * django STORAGE changes
        * see [6058](https://github.com/pulp/pulpcore/pull/6058)
    * python bindings updated by LOTS of changes
        * it is *likely* that plugin-tests *are going to break*
        * see [6138](https://github.com/pulp/pulpcore/pull/6138)
    * discussion
        * quba42: can we just move UB? or do we need to force 3.70 as LB?
            * *should* be able to just relax UB - but this is what the "lowerbounds" testing is aimed at finding
    * NOTE: UB can be relaxed to "<3.85"
        * discussion:
            * ggainey: is 15 releases good?
            * quba42: seems to be "reasonable"
            * quba42: is this too *long*?
### Action Items:
* ggainey to archive 2024 minutes
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39