Maintenance: Planio will be observing a scheduled maintenance window this Tuesday, November 5, 2024 from 03:00 UTC until 06:30 UTC to perform urgent network maintenance in our primary data center. Your Planio account will be unavailable during this maintenance window.
Issue #8091
closedCopying an advisory also copies over modulemds for some reason
Description
I noticed that module stream copying has changed behavior since Katello 3.17 (pulp-rpm 3.7.0). After some searching, I noticed that errata are also copying over modulemds and I'm not sure why. There doesn't seem to be a connection between the erratum in question and the copied modulemds. Dep solving is off.
Details:
Repository: clone Katello on GitHub and host this repo with the simple python http server https://github.com/Katello/katello/tree/master/test/fixtures/test_repos/zoo
Erratum to copy to from that repo to an empty repository: KATELLO-RHEA-2010:99143
Sample curl command that I used:
curl https://`hostname`/pulp/api/v3/rpm/copy/ -H "Content-Type: application/json" --cert /etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key --request POST --data '{"config": [{"source_repo_version": "/pulp/api/v3/repositories/rpm/rpm/c59c72dd-3e6f-443e-9e15-10c01aa3012b/versions/1/","dest_repo": "/pulp/api/v3/repositories/rpm/rpm/b5f4217b-f6f4-434d-b2db-d483d9d0ae1a/","content": ["/pulp/api/v3/content/rpm/advisories/68a00111-03fa-4ba4-ba32-e3eb54976bb6/"]}], "dependency_solving": "false"}'
You should see that 6 modulemds are copied.
Related issues
Updated by iballou almost 4 years ago
I noticed the same issue when randomly grabbing the RHEA-2012:0055 erratum from https://fixtures.pulpproject.org/rpm-with-modules and trying to copy it to an empty repo. The resulting repo version had all the modulemds in it for some reason.
Updated by iballou almost 4 years ago
I'll just add that the tests I did above with curl were with the following Pulp versions:
pulp-2to3-migration (0.6.0) pulp-ansible (0.6.0) pulp-certguard (1.1.0) pulp-container (2.2.0) pulp-deb (2.8.0) pulp-file (1.5.0) pulp-rpm (3.8.0) pulpcore (3.9.0)
I noticed the underlying module stream issue on pulp-rpm 3.7.0 that made me investigate but didn't test the exact case I mentioned above.
Updated by dalley almost 4 years ago
- Severity changed from 2. Medium to 3. High
- Triaged changed from No to Yes
- Sprint set to Sprint 88
Updated by iballou almost 4 years ago
- Priority changed from Normal to High
Changing priority to high because this is blocking Katello's upgrade to Pulpcore 3.9.
Updated by dalley almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by pulpbot almost 4 years ago
- Status changed from ASSIGNED to POST
Updated by iballou almost 4 years ago
- Related to Backport #8121: Backport Request: 8091 (Copying an advisory also copies over modulemds for some reason) to 3.7 added
Added by dalley almost 4 years ago
Updated by dalley almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset 1652026913308e8348543af6f62c3b5c5f89985b.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Fix all modules accidentally being copied
closes: #8091 https://pulp.plan.io/issues/8091