Project

Profile

Help

Test #4459

Unable to sync 3 SLES Update repositories

Added by bherring 8 months ago. Updated 5 months ago.

Status:
CLOSED - COMPLETE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Pulp 2
Sprint:

Description

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
dupe_srpm_repodata.tgz (1.22 MB) daviddavis, 02/08/2019 03:29 PM dupe_srpm_repodata.tgz

Related issues

Copied from RPM Support - Issue #4397: Unable to sync 3 SLES Update repositories CLOSED - CURRENTRELEASE Actions

Associated revisions

Revision a98c4c3a View on GitHub
Added by bherring 7 months ago

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.

See: https://pulp.plan.io/issues/4459

closes #4459

History

#1 Updated by bherring 8 months ago

  • Copied from Issue #4397: Unable to sync 3 SLES Update repositories added

#2 Updated by bherring 8 months ago

  • Status changed from MODIFIED to ASSIGNED

#3 Updated by bherring 8 months ago

  • Assignee set to bherring

#4 Updated by bherring 8 months ago

  • Status changed from ASSIGNED to MODIFIED

#5 Updated by bherring 8 months ago

Notes

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

#6 Updated by bherring 7 months ago

  • Status changed from MODIFIED to ASSIGNED

#7 Updated by bherring 7 months ago

  • Status changed from ASSIGNED to MODIFIED

#8 Updated by bherring 7 months ago

  • Priority changed from Normal to High

#9 Updated by bherring 7 months ago

  • Sprint/Milestone set to 2.19.0

#10 Updated by bherring 7 months ago

  • Sprint/Milestone deleted (2.19.0)

#11 Updated by bmbouter 6 months ago

  • Tags Pulp 2 added

#12 Updated by bherring 5 months ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF