Bug 1039947

Summary:	Fail to access mirror1.ops.rhcloud.com
Product:	OpenShift Online	Reporter:	Lei Zhang <lzhang>
Component:	Image	Assignee:	Ben Parees <bparees>
Status:	CLOSED CANTFIX	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	2.x	CC:	tdawson, xtian
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:	2014-01-24 22:11:22 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:

Description Lei Zhang 2013-12-10 11:59:25 UTC

Description of problem:
It fails to access mirror1.ops.rhcloud.com, as a consequence, the builds relying on it will always fail. This problem affects all JBoss cartridges:

remote: Downloading: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD FAILURE
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Total time: 3:27.382s
remote: [INFO] Finished at: Tue Dec 10 06:43:50 EST 2013
remote: [INFO] Final Memory: 5M/78M
remote: [INFO] ------------------------------------------------------------------------
remote: [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to nexus (http://mirror1.ops.rhcloud.com/nexus/content/groups/public): Error transferring file: Connection reset -> [Help 1]

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

How reproducible:
always

Steps to Reproduce:
1. try to download rhc client from mirror1
2. create a jboss app (jbossas, jbosseap, jbossews)
3. make some change and trigger a build via Git

Actual results:
The connection to the mirror1 is reset and building the JBoss app fails:
remote: Downloading: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD FAILURE
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Total time: 3:27.382s
remote: [INFO] Finished at: Tue Dec 10 06:43:50 EST 2013
remote: [INFO] Final Memory: 5M/78M
remote: [INFO] ------------------------------------------------------------------------
remote: [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to nexus (http://mirror1.ops.rhcloud.com/nexus/content/groups/public): Error transferring file: Connection reset -> [Help 1]

Expected results:
mirror1.ops.rhcloud.com should be reliable enough, or we could offer some alternatives automatically if one of the mirrors is down.

Additional info:

Comment 1 Troy Dawson 2013-12-10 16:34:44 UTC

mirror1.ops and mirror2.ops were updated yesterday to RHEL 6.5.  Although mirror2.ops updated correctly and worked properly, mirror1.ops worked for a while and then had issues with httpd staying alive.  It has now been fixed, but we are still investigating the issue.

As for having more than one machine listed (having mirror2.ops would have worked) I agree with you.  I do not have the java/xml skills necessary for that.

Comment 2 Troy Dawson 2013-12-10 20:32:23 UTC

Because the servers have been fixed, I am changing the severity from high to medium.  This bug is no longer blocking.

I am switching this over to the cartridge component because the cartridge should be able to fail over from mirror1 to mirror2 to prevent this from happening in the future.

Comment 3 Ben Parees 2014-01-24 22:11:22 UTC

Based on my research there actually is no way to specify more than one url for a given mirror, or more than one mirror for a given repository.
http://maven.apache.org/guides/mini/guide-mirror-settings.html

"Note that there can be at most one mirror for a given repository. In other words, you cannot map a single repository to a group of mirrors that all define the same <mirrorOf> value."

It's a strange limitation, but it seems like it would take a maven change to fix.