Actions
Issue #8091
closedCopying an advisory also copies over modulemds for some reason
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 88
Quarter:
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
Actions
Fix all modules accidentally being copied
closes: #8091 https://pulp.plan.io/issues/8091