Project

General

Profile

Actions
Copy link

Bug #30752

closed

Set sles_auth_token in yum-repository form for synching SLES-repos from SCC

Added by Markus Bucher over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Justin Sherrill
Category:
Repositories
Target version:
Katello 3.17.0
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/Katello/katello/pull/8928
Fixed in Releases:
Katello 4.0.0
Found in Releases:
Katello 3.16.0
Red Hat JIRA:

Description

To sync SLES Repositories from Suse Customer Center an additional authentication-token needs to be added to the repository URL.
With pulp2 it was enough to add `?<TOKEN>` to the end of the repository-url.

Pulp3-RPM requires to supply the token as a separate parameter when creating the Remote: https://pulp-rpm.readthedocs.io/en/latest/workflows/create_sync_publish.html#configuration-for-sles-12-repository-with-authentication

This error occurs when using foreman_scc_manager plugin: https://github.com/ATIX-AG/foreman_scc_manager/issues/43

Actions
Copy link
 #1

Updated by Chris Roberts over 4 years ago

  • Category set to Repositories
  • Target version set to Katello 3.17.0
  • Triaged changed from No to Yes
Actions
Copy link
 #2

Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Justin Sherrill
  • Pull request https://github.com/Katello/katello/pull/8928 added
Actions
Copy link
 #3

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases Katello 4.0.0 added
Actions
Copy link
 #4

Updated by Justin Sherrill over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF