Project

Profile

Help

Issue #2279

Pulp yum_importer fails when syncing SuSE repositories

Added by Alex.Bron almost 4 years ago. Updated over 1 year ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.10.0
Platform Release:
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

After upgrading Pulp from 2.9 to 2.10, a repo sync run will fail for most of the Suse repositories. After enabling debug mode, it was found that the repo sync run attempts to import the src.rpm files which are not available. It would be nice to be able to skip srpm, but that is not a supported type for the --skip option.


Related issues

Related to Pulp - Task #2383: Test recent pulp syncing to SuSE repositoriesCLOSED - WORKSFORME

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by semyers almost 4 years ago

Can you provide the feed URL of a specific repository demonstrating this problem?

#2 Updated by Alex.Bron almost 4 years ago

One of the failing repos is https://updates.suse.com/repo/$RCE/SLE11-HAE-SP4-Pool/sle-11-x86_64/
Our setup is that we use a SuSE SMT server for obtaining repo information from SuSE, and then we have Pulp build repositories from that SuSE SMT content. I have set the SuSE SMT to also mirror src.rpms but apparently for SLE11-HAE-SP4-Pool there are no src.rpms available. This makes the Pulp importer fail...

#5 Updated by semyers almost 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to semyers

#7 Updated by semyers almost 4 years ago

  • Triaged changed from No to Yes

#9 Updated by semyers almost 4 years ago

  • Related to Task #2383: Test recent pulp syncing to SuSE repositories added

#10 Updated by semyers almost 4 years ago

I did some basic testing without involving SMT which worked correctly, so I'll look into getting SMT set up similarly and see what kind of repos it puts together for pulp to try to sync.

#11 Updated by semyers over 3 years ago

Alex.Bron wrote:

One of the failing repos is https://updates.suse.com/repo/$RCE/SLE11-HAE-SP4-Pool/sle-11-x86_64/
Our setup is that we use a SuSE SMT server for obtaining repo information from SuSE, and then we have Pulp build repositories from that SuSE SMT content. I have set the SuSE SMT to also mirror src.rpms but apparently for SLE11-HAE-SP4-Pool there are no src.rpms available. This makes the Pulp importer fail...

I don't have access to the HAE line of products, but every other repo I've tested (SLES 11 and 12) has synced correctly for me.

Does pulp fail when mirroring SLE11-HAE-SP4-Pool directly from suse/novell with mirroring credentials, without SMT in the middle? If so, can you provide detailed logging of the failure?

#12 Updated by semyers over 3 years ago

Following up, I'm proposing to close this, either as not a bug or wontfix.

We'll happily reopen it if logging shows that pulp is unable to sync from the official SUSE repositories; at the moment it sounds like SMT is publishing a repository whose metadata says SRPMs are available in that repo, when in fact they are not. That repository is broken.

It does sound like adding the SRPM type to the list of supported skip types would get around this issue, so I'll make sure we've got an issue tracking that enhancement before closing this one.

#13 Updated by semyers over 3 years ago

  • Status changed from ASSIGNED to CLOSED - NOTABUG

Closing as notabug since I'm unable to reproduce. Please reopen if you're able to reproduce this without SMT as a middleman between the official repos and Pulp.

#14 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF