Synchronize repository - Sync Status warning

Support
1

Problem:
When trying to synchronize the official “Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8” repository the synchronization task fails with the following error:

Error message: the server returns an error
HTTP status code: 400
Response headers: {"date"=>"Thu, 22 Apr 2021 06:12:23 GMT", "server"=>"gunicorn/20.0.4", "content-type"=>"application/json", "vary"=>"Accept,Cookie", "allow"=>"GET, POST, HEAD, OPTIONS", "x-frame-options"=>"SAMEORIGIN", "content-length"=>"44", "via"=>"1.1 hostname.fqdn", "connection"=>"close"}
Response body: {"base_path":["This field must be unique."]}

Expected outcome:
A successful synchronization of the repository. Also other repositories do not work

Foreman and Proxy versions:
Foreman: 2.3.3
Katello : 3.18.2.1
Pulp: 2.1.0
Pulp Server version: 2.21.5

Distribution and version:
https:// Index of /releases/2.3/el7
https:/ /fedorapeople.org/groups/katello/releases/yum/3.18/katello/el7/$

Other relevant data:
OS: Centos 7
pulp mountpoint is on a remote NFS share
no other modifications - standard installation via https:// Foreman :: Plugin Manuals

Thanks for your support

2

I’m also getting this issue - on a fresh Katello 4.0 GA install.

Repos failing:
CentOS 7 Base
CentOS 7 Updates
Foreman Client

Repos succeeding:
EPEL
CentOS 7 Extras

3

Same here. Recently upgraded to katello 4 GA

Repos failing:
Ubuntu 18
Ubuntu 20

Resumed the task and it’s been stuck on 72% complete for 24 hours now …

4

Hi folks,

If you’re on Katello 3.18, try this patch out: https://github.com/Katello/katello/commit/b4ff8a49f1489642cb71edde3587afb46d3a6825.patch

If you’re on Katello 4.0, try this patch out: https://patch-diff.githubusercontent.com/raw/Katello/katello/pull/9193.patch

The Katello 4.0 patch contains a bunch of test file updates that won’t exist on your production machines. Just skip the “can’t find file to patch” errors for all of the /test/fixtures/vcr_cassettes/... files.

Let me know if you have any troubles with the patch or if it doesn’t help. These patches will be included in the next point releases of both Katello 3.18 and 4.0.

1 Like
5

Did any of you have failed or canceled tasks relating to these repositories before seeing this error?

6

Hello,
sorry I cant apply the patch at the moment as we did a new installation from scratch with Foreman 2.4/Katello 4.0.
At the moment the offical RedHat repositories are synced without a problem.

If the error appears again, we will apply the patch.

Thank you already for your help. And good to see that help is provided via the forum

Best Regards,

1 Like