Issue #2279
closed
Pulp yum_importer fails when syncing SuSE repositories
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.
Can you provide the feed URL of a specific repository demonstrating this problem?
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...
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
- Triaged changed from No to Yes
- Related to Task #2383: Test recent pulp syncing to SuSE repositories added
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.
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?
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.
- 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.
Also available in: Atom
PDF