Bug 1581675 - "yum copr enable" for existing copr repositories gives Errno 14 - 404
Summary: "yum copr enable" for existing copr repositories gives Errno 14 - 404
Keywords:
Status: CLOSED DUPLICATE of bug 1580451
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-23 11:45 UTC by Daniele Branchini
Modified: 2018-05-24 11:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-24 11:04:47 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.