Bug 1900300 - copr repo via ipv6
Summary: copr repo via ipv6
Keywords:
Status: CLOSED DUPLICATE of bug 1232949
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Copr Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-22 01:44 UTC by Ali
Modified: 2020-12-11 18:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-11 18:39:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Ali 2020-11-22 01:44:44 UTC
Description of problem:

Using copr, after the build process the Repo Download link
doesn't work in an ipv6 only setup and we are at the end of 2020.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. build any package on copr (or use any already build package)
2. follow the download link in the 'Repo Download' tab
3. remove any ipv4 address from your client host and follow the download link again.

Actual results:
curl https://copr.fedorainfracloud.org/coprs/alijkl/etcd/repo/epel-8/alijkl-etcd-epel-8.repo
curl: (7) Couldn't connect to server


Expected results:
the repo file should be available via ipv6
and of course the contain as well (the rpm data and metadata) should be reachable via ipv6.
 
Additional info:
while 'https://download.copr.fedorainfracloud.org' is reachable via ipv6
trying to access the real contain (the location epel-8-$basearch/ in my case)
redirect to https://copr-be.cloud.fedoraproject.org which not reachable via ipv6 as well.

 curl https://copr-be.cloud.fedoraproject.org
curl: (7) Couldn't connect to server

Comment 1 Pavel Raiskup 2020-12-11 18:39:38 UTC
Thank you for the report!  We are tracking ipv6 support in different bug, so I'm
moving your info there.

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


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