Bug 1232949

Summary:	RFE: support copr clients on ipv6 only networks
Product:	[Community] Copr	Reporter:	L.L.Robinson <junk>
Component:	frontend	Assignee:	Copr Team <copr-team>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ali.bendriss, fedora, lsjun, praiskup
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-22 16:23:53 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 L.L.Robinson 2015-06-17 21:58:59 UTC

Description of problem: copr cannot download SRPMS from an IPv6 only host  


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


How reproducible: always


Steps to Reproduce:
1.publish SRPM to host accessible only by IPv6 e.g. http://buildserver.therobinsonfamily.net/SRPMS/
2.????
3.Fail

Actual results:Build fails with: 
Error Downloading http://buildserver.therobinsonfamily.net/SRPMS/tty-solitaire-git-4.20150530git343a55ca.fc22.src.rpm: HTTPConnectionPool(host='buildserver.therobinsonfamily.net', port=80): Max retries exceeded with url: /SRPMS/tty-solitaire-git-4.20150530git343a55ca.fc22.src.rpm (Caused by <class 'socket.error'>: [Errno 101] Network is unreachable)


Expected results: SRPM to be built


Additional info:

Comment 1 Miroslav Suchý 2015-06-18 06:07:19 UTC

Copr is deployed as instance on OpenStack. And OpenStack still does not fully support IPv6.
This will take long. Probably before OS will start supporting IPv6, we will implement uploading of SRPM.

Comment 2 Pavel Raiskup 2020-03-17 08:38:38 UTC

*** Bug 1812077 has been marked as a duplicate of this bug. ***

Comment 3 Pavel Raiskup 2020-12-11 18:38:24 UTC

Copr now lives mostly in AWS, and we should be able to configure ipv6 there.
This needs to be done in cooperation with fedora infra people because we
(copr team) don't have permissions to configure subnets.

This should resolve also the `repo` files downloaded by `dnf copr enable`.

Comment 4 Pavel Raiskup 2020-12-11 18:39:36 UTC

*** Bug 1900300 has been marked as a duplicate of this bug. ***

Comment 5 Pavel Raiskup 2020-12-11 18:40:47 UTC

Not only frontend, but backend needs fix too, from bug 1900300:

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

The CDN redirects DNS queries to copr-be.cloud.* if particular file isn't
cached.

Comment 6 Pavel Raiskup 2021-01-22 16:23:53 UTC

AWS environment allowed us to setup IPv6 networking.  So copr-cli (communicates
with copr-frontend should work) same as downloading the built results
(downloads from copr-backend) should work.