Pulpcore/katello/pulp_deb integration meeting

# 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 ``` # 2026 ## 2026-06-02 1000-1030 GMT-5 ### Attendees: ### Regrets: ### Agenda: * Previous AIs: * iballou to pull together katello-branch-decision-dates for ATIX to see/know ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2026-05-05 1000-1030 GMT-5 ### Attendees: ggainey, iballou, sjha, pbrochado, quba62, mbucher ### Regrets: ### Agenda: * Previous AIs: * ~~ggainey: to take "Triage-Needed" response to triage-mtg~~ * ~~iballou: will review coderabbit findings from [katello/11567](https://github.com/Katello/katello/pull/11567) and see which if any really need to be addressed~~ * settled and merged * ~~mbucher: to open RfC RE incremental-CV/errata update issue from 2026-03-03~~ -> [RFC: Add Errata should add Incremental-CV to newer CVs as well](https://community.theforeman.org/t/rfc-add-errata-should-add-incremental-cv-to-newer-cvs-as-well/46359) * https://projects.theforeman.org/issues/37710 Do we want to pick this back up? * having trouble reproducing? * let's see if it is still useful - and close this out if not? * [quba42] Challenges around pulp_deb plugin maintenance, release conventions, and Katello packaging: * Exhibit A: https://github.com/pulp/pulp_deb/pull/1369#discussion_r3181233251 * Katello fix will require unreleased: https://github.com/pulp/pulp_deb/pull/1424 * Katello feature will require WIP: https://github.com/pulp/pulp_deb/pull/1392 * discussion ensues * there's no "solution" to the intractable release-issues discussed - but everyone is, at least, sympathetic * can we solidify katello-branch-decision-dates for ATIX to see/know? iballou to look into making this possible ### Action Items: * iballou to pull together katello-branch-decision-dates for ATIX to see/know * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2026-04-07 1000-1030 GMT-5 ### Attendees: ggainey, pbrochado, sjha, iballou, quba42, mbucher ### Regrets: hstct ### Agenda: * Previous AIs: * ~~someone-katello to open a community discussion RE angular-to-react scheduling/process~~ * https://community.theforeman.org/t/ui-plan-transitioning-from-pf3-erb-and-angular-to-patternfly-6/45946 * mbucher to open RfC RE incremental-CV/errata update issue from 2026-03-03 * https://projects.theforeman.org/issues/37710 Do we want to pick this back up? * Missed discussion because mtg-organizer skipped a groove * don't push the release-button * RE Quirin's "why is the core/107 tag not pointing where it should?" * Pulp project-team is working to fix the release-process, stay tuned * triage-needed label in pulp_deb * is it useful for you at all? * sometimes, but not systematically * "no strong opinions" * AI: ggainey to take that to triage-mtg * [quba42, hstct on PTO] https://github.com/Katello/katello/pull/11567 Has already received significant review/nearing completion. * New development: New coderabbitai added its 2ct. Unsure about handling the new tool that is late to this particular party. * AI: iballou: will review coderabbit findings and see which if any really need to be addressed * [quba42] I have (almost certain) abandoned the approach in https://github.com/Katello/katello/pull/11631 * However, the new approach requires a change in pulp_deb to land. The change is [merged in pulp_deb](https://github.com/pulp/pulp_deb/pull/1424), and I can release at any time. How close are we to new pulpcore version packaging? * DON'T RELEASE YET! (7-APR) * if we can fix release-process "soon", pulp_deb would like a new pulp-deb-Y to be packaged as part of katello/4.21 * We (Katello) are looking more into containerized Foreman, have others been looking? * heavy testing in process * ATIX has taken a "first light" look * why require Vagrant for dev-env? ### Action Items: * ggainey to take "Triage-Needed" response to triage-mtg * iballou: will review coderabbit findings [katello/11567](https://github.com/Katello/katello/pull/11567) and see which if any really need to be addressed * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2026-03-03 1000-1030 GMT-5 ### Attendees: quba42, mbucher, bsuttner, iballou, sjha, hstct, pbrochado, ggainey ### Regrets: ### Agenda: * Previous AIs: * (m-bucher) Katello-UI: is there a roadmap for migrating pages to React? * no "schedule", but a list of pages-to-be-affected, prioritized * maybe open a community post with remaining work - get some help? * some changes will impact community-users more than others (e.g. page-merges) * AI: someone-katello to open a community discussion * (m-bucher) Katello-UI RfC: add Errata to 'all newer' ContentView-Versions Example: 1. CV has versions 1(PROD), 2(Test), 3(Library) 1. Erratum ERR1 is Applicable to all versions 1. Host A on PROD will get ERR1 fixed by creating Incr.Update to Version 1 => 1.1 CV-Version 2, 3 will not get Incr.Updates, if no Hosts are subscribed! 2. when PROD moves to CV-version 2, all **new** hosts created will not have ERR1 fixed⚡ * does this make sense as an RfC? * If so - where/how should the UI be changed? * Incremental-CV-Update definitely needs love - today users generally use hammer to accomplish Things * https://issues.redhat.com/browse/SAT-3304 * AI: mbucher to open RfC "somewhere" * discussion about where this would happen ensues - implementation discussion will need to happen in the RfC * prob could stand to query community-users how this functionality could be approached? (host-centric vs repo/CV-centric) * [quba42]: Structured APT cleanup: https://github.com/Katello/katello/pull/11631 * There is a known edge case that I would like to fix as a follow up task. A version of the issue existed in the past, but now it is a hard error during CV version creation, rather than silently letting you create a broken CV version. I would argue that is already an improvement. * [quba42]: Packaging (nearly?) ready for ACS for deb content: https://github.com/Katello/katello/pull/11567 * Depends on pulp_deb 3.8.0, which is currently only available in "nightly" pulpcore-packaging. Can we add this to a Katello version that does not switch to a new pulpcore repo version? * [iballou] Looking at orphan-cleanup PR from bsuttner * when will katello require/enable pulp-domains? * maybe look into pulp-labels - migration issues? * are labels indexed? * https://github.com/Katello/katello/pull/11658 ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2026-02-03 1000-1030 GMT-5 ### Attendees: ### Regrets: ### Agenda: * Previous AIs: * ggainey to archive 2025 * https://hackmd.io/@pulp/pulp-deb-katello-integration_2025 * mtg skipped due to various conflicts and no current agenda ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2026-01-06 1000-1030 GMT-5 ### Attendees: ggainey, samir, pbrochado ### Regrets: ### Agenda: * Previous AIs: * Welcome to 2026! * core/3.100 being released **today** * update plugin pulpcore UB to core<3.115 please * lots of Django5 discussion ensues ### Action Items: * ggainey to archive 2025 * https://hackmd.io/@pulp/pulp-deb-katello-integration_2025 * ggainey to move next Pulp/katello mtg to *next* Weds due to PTOs * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 # 2025 * Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2025 # 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`