2021 notes, pulp_rpm team mtg

# 2022 notes, pulp_rpm team mtg ## 2022 ### Dec 16, 2022 Pulp 3: * ppicka updated status of domains/pytest * #soon * talking w/ lmjachky RE pytest conversions Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### Dec 9 * libmodulemd-removal tripping over Bad Modulemds in the wild * breaks nightlies * [ppicka] need to bring to the attention of modularity gang * DONE, specifications are more of a set of aspirational guidelines, really - we need to be more relaxed * Discussion around COPR's requirements * COPR may need its own CoprRpmRepository type? * needs investigation * COPR needs buildlogs, review-files, etc * need to be versioned just like RPM artifacts * or do they? * or a COPR subclass of pulp_rpm? * how does "make packages available immediately?" actually work? * multiple-advisories-with-same-id Fun * https://hackmd.io/@ggainey/dup_advisory_problem * domains * ensure added `unique_together` uses right fields * https://github.com/pulp/pulp_rpm/compare/main...pavelpicka:pulp_rpm:domains * `retrieve` for upload (core 3.22 feature) * please file issue for Domains/Upload behaviour change * advisories can't use "id" as a unique-together (alas) Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### Dec 1, 2022 Pulp 3: * Isolation on the domain level * AI: ppicka - find out if possible, if so start on the domains Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### Nov 3, 2022 Pulp 3: * Isolation on the domain level [ppicka] (as a continuation of `rbac`) * ``/pulp/domain/api/v3/`` & ``/pulp/content/domain`` * doesn't have to be enabled (if enabled it is one way ticket) * overview https://hackmd.io/n-OGwj3xQYapMsipzkgqbA?view * pytest usage - we have to convert before we move to domains * concurrent overlapping subrepo sync update ([2278](https://github.com/pulp/pulp_rpm/issues/2278)) * the news WAS All Bad * started a braindump here : https://hackmd.io/@ggainey/subrepo_problem * tl;dr: autopublish, mirror, and subreposyncs are all doing things inside one worker that Pulp architecture assumes are correctly-serialized events * supplied an Alternative #2, implemented in [PR 2851](https://github.com/pulp/pulp_rpm/pull/2851) * looks like it solves All The Things - please review/comment * multiple advisory problem ([2821](https://github.com/pulp/pulp_rpm/issues/2821)) * do we want to completely rethink "what happens when a sync delivers an advisory whose id exists in prev_version, but whose digest differs"? * e.g.: "Incoming always wins, duplicate-ids allowed. new_version has only the (new) incoming ids, existing in prev_version are removed." * Implications: merges never happen, we don't catch a number of "this is probably a Bad Idea" cases, code gets WAY simpler * the matrix of "how many with id-X are in prev, how many are incoming, What Do We Do?!?" is...painful * BZ triage: * https://bugzilla.redhat.com/show_bug.cgi?id=2016759 Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### October 21, 2022 Pulp 3: * Should we allow duplicate advisory-ids in a repo? [2821](https://github.com/pulp/pulp_rpm/issues/2821) * nightly-dnf will work if we allow * not sure what the results will be for already-relased dnf, or yum * not a libsolv solution, it's resolved inside dnf (and therefore may behave differently/badly for, say, zypper) * needs to stay prio-list due to number of cases associated * Discuss what to do about concurrent overlapping subrepo syncs [2278](https://github.com/pulp/pulp_rpm/issues/2278) * If we go down the "unique-name-per-repo" path - can we clean up resulting orphaned subrepos as a stage? * can it be done in the finalize_new_version? - yes, I think so! Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged issues: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed CI status check * https://github.com/pulp/pulp_rpm/actions?query=workflow%3A%22Pulp+Nightly+CI%2FCD%22 ### September 2 Pulp 3: * Kanban process adjustments - go through issues and labels and PRs * Advisory package unique constraint * update uniqueness to deduplicate at sync time + data repair * no import/export fix needed if above fix is done * there was mention same issue for UpdateRecord on #pulp * rpm plugin pulpcore compatibility for 3.18 * Release blockers Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged issues: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed CI status check * https://github.com/pulp/pulp_rpm/actions?query=workflow%3A%22Pulp+Nightly+CI%2FCD%22 3-month planning checkin (every 1.5 months): ### August 25th Pulp 3: * https://github.com/pulp/pulpcore/issues/3135 has been filed, may or may not be specific to the RPM plugin, possibly concurrency related? Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### August 18th Pulp 3: https://community.theforeman.org/t/sync-errors-on-all-syncs-including-the-initial-sync-between-new-katello-server-and-content-proxy/29577/9 Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### August 11, 2022 Pulp 3: * Should we (officially) plan to have meetings every other week? * sounds like every-other is a good idea * if so - have it on weeks that are NOT sprint-planning weeks * Pulp in Gitlab (meeting next week) * initial exploratory get-together * EXD updates * https://issues.redhat.com/browse/RHELWF-7304 * https://issues.redhat.com/browse/RHELDST-11565 Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### Jul 28, 2022 Pulp 3: * CI fixes 3.14 and 3.17 * Investigation in progress * backports * Action: show the list to Ian * 3.18 release blockers Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### July 14, 2022 Pulp 3: * rpm/3.18 release? * may fix https://github.com/pulp/pulp_rpm/issues/2403 , which is being discussed in #pulp * Fedora and module obsoletes Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### June 30th, 2022 Pulp 3: * Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### June 23rd, 2022 Pulp 3: * CI Broken everywhere :( * How to release support for module obsoletes and get it into a shipping release * This probably wouldn't become a (significant) problem for 6-12 months, but we want to avoid it becoming one * Do we need to shuffle RBAC out of 3.18? Or break our rules for 3.17? * No shuffling, we should re-order commits but not plan to release it immediately for 3.17 Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### June 16th, 2022 Pulp 3: * 3.18 release tasks * Early next week - needs to release before 3.20 * What I would like to go in: * package retention fix * conflicting content being published * remove location_base / location_href * Several open questions still, need answers / reviews, take a look at these when you can * https://github.com/pulp/pulp_rpm/pull/2547 * https://github.com/pulp/pulp_rpm/pull/2586 * Preliminary plan: make 3.17 compatible with pulpcore 3.20 * Module obsoletes support * Same "snippet" approach as other module data? * yes Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### March 31, 2022 Pulp 3: * backporting discussion * should we wait before backporting? * at a minimum, perhaps we need to be more deliberate about backport/release Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### March 24, 2022 Pulp 3: * New release? * yes, 3.14 and 3.17 * Prompt about libdnf? * Pulp 2: Open PRs: https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A"Rpm+Nightly+CI%2FCD" ### March 10, 2022 Pulp 3: * rbac * adding basic tests Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Last week stories and tasks  * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2022-02-17+-label%3Aissue Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### March 3, 2022 Pulp 3: * DNF team will be tied up with a rewrite of DNF for the forseeable future, 12-18 months. Limited availability for cooperation on createrepo_c * rbac * no content protection (not implemented by core) * will post a thread on Discourse, reach out to Neal Gompa Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Last week stories and tasks  * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2022-02-24+-label%3Aissue Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### February 24, 2022 Pulp 3: * Memory consumption PR(s) * https://github.com/pulp/pulp_rpm/pull/2411 * rbac * init doc for rbac https://hackmd.io/q9mXbOXKSbyDNRqp6OBzmA * let's start with simple, coarse-grained Roles * 'Admin' - CURLD on Repository/Remote/Content * 'Viewer' - Read-only access * let's get a discussion going on Discourse RE our current plans * ping some specific community-members who have expressed interest/needs for this Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Last week stories and tasks  * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2022-02-17+-label%3Aissue Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI status check * https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A%22Rpm+Nightly+CI%2FCD%22 ### February 17, 2022 Pulp 3: * migration issue https://github.com/pulp/pulp_rpm/issues/2405 * problem may only show up on older Postgres? * one upstream user was on pgres-10, prob went away w/ newer pgres * try making migration "non-atomic"? * has some downsides * or, split migration into two? * https://stackoverflow.com/questions/28429933/django-migrations-using-runpython-to-commit-changes * concerns about what happens if user has already-applied existing migration Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Last week stories and tasks * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2022-01-27+-label%3Aissue Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed CI status check * https://github.com/pulp/pulp_rpm/actions?query=workflow%3A%22Pulp+Nightly+CI%2FCD%22 * what happened to BaseOs/kickstart?!? * dalley to confirm, need to update tests if so ### January 27, 2022 Pulp 3: * Import / Export + kickstart trees * https://bugzilla.redhat.com/show_bug.cgi?id=2040870 * Has never worked properly * ggainey Has A Sad, is working on a possible fix * Distribution tree issue - kickstart-subrepos can have versions, we assume "latest" is always good * https://github.com/pulp/pulp_rpm/issues/2304#issuecomment-1019297646 * Nigh-impossible to backport * Tanya will talk to Dennis * NFS Fun : https://bugzilla.redhat.com/show_bug.cgi?id=2041508 Pulp 2: Open PRs: * https://github.com/pulp/pulp_rpm/pulls Last week stories and tasks * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2022-01-20+-label%3Aissue Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+-label%3Atriaged CI status check * https://github.com/pulp/pulp_rpm/actions?query=workflow%3A%22Pulp+Nightly+CI%2FCD%22 ### January 13, 2022 Pulp 3: * Backport changelog limit? https://github.com/pulp/pulp_rpm/pull/2333 * yes! * Tool to purge changelogs already in the database? * if it's a sep tool, removes potentially long-running 'fix' from a user's update-window * allow-'0' implications? * what's the final "dnf --changelog" behavior if this happens? * do we know exactly when infra-chg resulted in RHEL7 getting all-changelogs again? * make sure any testing of this, includes end-to-end (ie, client using dnf against the resulting repo) * add a 'synthetic' changelog-entry saying "changelogs trimmed by tool-X on date YYYY-MM-DD" * should run that idea past EXD as well * or, just set floor at '1'? * How do we ship plugin-specific tooling? * Note: Pulp2 needs a diff (much harder?) solution for cleanup due to how changelog-snippets are stored * Observability PR - what if it was a much smaller text file, no data dump * https://github.com/pulp/pulp_rpm/pull/2344 * reduce to just "packages depsolve decided it needed 'extra', and why" * We could theoretically always keep them - but we still might want to handle cleanup * use syslog, not do our own file writing? Pulp 2: * bad-primary.xml bz getting attention again * https://bugzilla.redhat.com/show_bug.cgi?id=1948930 Open PRs: * https://github.com/pulp/pulp_rpm/pulls Un-triaged bugs: * https://github.com/pulp/pulp_rpm/issues Last week stories and tasks: * https://bit.ly/3dCTomw CI status check * https://github.com/pulp/pulp_rpm/actions?query=workflow%3A%22Pulp+Nightly+CI%2FCD%22 ###### tags: `RPM`, `Minutes`