Bug 1581675

Summary:	"yum copr enable" for existing copr repositories gives Errno 14 - 404
Product:	[Community] Copr	Reporter:	Daniele Branchini <dbranchini>
Component:	frontend	Assignee:	Miroslav Suchý <msuchy>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	dcesari, praiskup
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-24 11:04:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniele Branchini 2018-05-23 11:45:00 UTC

Description of problem:

We're trying to enable some existing copr repositories from different CentOS7 x86_64 servers and containers, but in the past fews days always exits with the message:
`[Errno 14] HTTPS Error 404 - Not Found`

Other CentOS7 servers that have already those repo enabled works correctly.
Fedora repositories don't seem affected.

I tried with the "Regenerate Repository" button on the copr repo I manage, I tried restarting a build but nothing changed.

Version-Release number of selected component (if applicable):
CentOS Linux release 7.5.1804 (Core)
yum-3.4.3-158.el7.centos.noarch
yum-plugin-copr-1.1.31-45.el7.noarch

How reproducible:

Steps to Reproduce:
1. `yum install yum-plugin-copr`
2. `yum copr enable simc/stable` (or other centos7 x86_64 repos)

Actual results:
`Error: [Errno 14] HTTPS Error 404 - Not Found`

Expected results:
enabling copr repo

Additional info:

Comment 1 Davide Cesari 2018-05-23 12:32:43 UTC

I noticed it works by adding an explicit chroot argument:

yum copr enable simc/stable epel-7

it seems that without chroot the default would be `epel-7-x86_64`. There is probably some misalignment between copr plugin and the Fedora copr server on older distros.

Comment 2 Miroslav Suchý 2018-05-24 11:04:47 UTC


*** This bug has been marked as a duplicate of bug 1580451 ***