# Pulp-Katello-community meeting

See also: https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

## Overview
* Purpose: Facilitate release-planning between Pulp3, Katello, and pulp_deb releases
* Attendees: pulpcore, katello, pulp_deb reps; others as needed

## Template

##  YYYY-MM-DD 1000-1030 GMT-5
### Attendees: 
### Regrets:
### Agenda:
* Previous AIs:
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

# 2025
## 2025-08-05 1000-1030 GMT-5
### Attendees:
### Regrets:
### Agenda:
* Previous AIs:
### 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

# 2024
* Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2024

# 2023
* Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2023

# 2022
* Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2022

# 2021
* Archived : https://hackmd.io/@pulp/pulp-deb-katello-integration_2021

###### tags: `Minutes`