Hide Forgot
Created attachment 1192932 [details] Failed build log for Jboss WebServer Tomcat 7 Image Description of problem: Builds are failing due to "peer not authenticated" error Version-Release number of selected component (if applicable): OpenShift Master: v3.2.1.9-1-g2265530 Kubernetes Master: v1.2.0-36-g4a3f9c5 How reproducible: When using an image from xPaaS suite it sometimes fails with the error "Peer Not authenticated" When applying this WA from version 3.1 it still fails with ""Remote host closed connection during handshake: SSL peer shut down incorrectly"" - name: MAVEN_ARGS_APPEND value: "-e -Dmaven.wagon.http.ssl.insecure=true -e -Dmaven.wagon.http.ssl.allowall=true -e -Dhttps.protocols=TLSv1,SSLv3" Additional info: Please note that we are using a corporate Proxy. Also we had failed builds due to bug 1349224 and after applying the work around we jumped to this issue. Support Case for reference: https://access.redhat.com/support/cases/#/case/01677396 Original bug for your reference: https://bugzilla.redhat.com/show_bug.cgi?id=1349224
Created attachment 1192933 [details] Failed build log for JWS Tomcat 8 Image
Created attachment 1192934 [details] Failed build log for EAP 6 Image
PRIVATE: From the EAP log it looks as if maven central closed the connection early Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact org.jboss.logging:jboss-logging:pom:3.1.0.CR2 from/to central (https://repo1.maven.org/maven2): Remote host closed connection during handshake
PRIVATE: Tomcat image appears to show the same Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.5 from/to central (https://repo1.maven.org/maven2): Remote host closed connection during handshake
PRIVATE: BTW neither log mentions anything about "Peer Not authenticated". I notice that you mention a corporate proxy, could this be closing the connection down? Have you looked at the network traffic to see what is happening or turned on the tls/ssl debugging?
Apologies, I thought this was a support case and coming from a RH employee. I'm making my private comments public.
Hello, Thank you for your feedback. We no longer use a corporate proxy because of the complexity that it induced and the issues that we had with builds. Also it seems that Openshift doesn't have a full support on using proxies (Red Hat doesn't recommend using them). Thank you again for your support. Have a good day, Bogdan Calomfirescu
Since this seems to be related to the network infrastructure rather than the image I'm now closing this as not a bug.