Unable to sync 3 SLES Update repositories
Filtering by srpm:
pulp-admin rpm repo create --repo-id testrepo --feed file:///home/vagrant/testrepo/ --skip srpm pulp-admin rpm repo sync run --force-full --repo-id testrepo
Causes the following error:
Malformed repository: metadata is missing for some packages in filelists.xml and in other.xml
While syncing without the srpm filter seems to work fine.
Test Specific Notes¶
- came from downstream
- create a specific fixture with SRPM duplication
Adding SRPM CLI test for --force-full with --srpm skip
Issue #4397 addressed an issue where duplicate SRPMS would fail
on sync when using `--srpm skip`.
Adding CLI test to ensure that in this scenario the SRPMS are
skipped on sync and no SRPMs are on the system.
Tested with duplicate SRPMs to verify the fix.
Added a case with normal SRPM test fixture to ensure basic
behavior has not changed.
Related to pulp-fixtures #119 created for this test.
Additional clarification on fixture verification
[12:58:04]<bherring>Question about https://pulp.plan.io/issues/4397 , when you have a moment [12:58:30]<bherring>1. Is --force-full really required to demonstrate the failure with `--skip srpm` duplication? I don't think it is [12:59:31]<bherring>2. When using `--skip srpm` we should be skipping all SRPMs on the sync (or the unit_type issued there). I am assuming that, while nice to have other unit types in a mixed repo, it isn't necessary to prove the functionality of this fix [12:59:56]<bherring>3. Using `--skip srpm` with a non-duplicated repo should not demonstrate this behavior, correct? [13:00:06]<bherring>(even before the fix was in-place) [13:05:29]<daviddavis> 1. no [13:05:43]<daviddavis> 2. correct [13:06:00]<daviddavis> 3. correct
- Status changed from ASSIGNED to MODIFIED
Applied in changeset pulp:pulp-2-tests|a98c4c3a91daca1d2c64be376df8c256609950a3.
Please register to edit this issue