Bug 1349224

i know the eap and jws images are supposed to autoconfigure the maven proxy settings if HTTP_PROXY/HTTPS_PROXY is set, not sure why it's not working for you.

The problem is likely that HTTP_PROXY is uppercase, and not lowercase. See https://bugzilla.redhat.com/show_bug.cgi?id=1348945#c4

@martin: again not the case, the issue here is that the middleware images explicitly expect a different set of proxy env variables that they use to configure maven/etc, and it does not align with the standard HTTP_PROXY/http_proxy variables.

Since image works well with it's special settings, remove the testblocker keyword
> $HTTP_PROXY_HOST
> $HTTP_PROXY_PORT
> $HTTP_PROXY_USERNAME
> $HTTP_PROXY_PASSWORD
> $HTTP_PROXY_NONPROXYHOSTS

Test with 
registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat8-openshift            latest              8bcae5669106        3 weeks ago         735.8 MB
registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift            latest              fb6eaa939b95        3 weeks ago         733.8 MB

build successfully under proxy

Lowering severity as there is viable workaround of using uppercase variables.

Environment variable case is not an issue.  Not sure what was tested here.  Can you provide details related to the tests?


Work for this issue will continue on the linked JIRA - https://issues.jboss.org/browse/CLOUD-865.

The same reproduce steps and openshift master config in description

The tests indicated you used the following images for Tomcat (7 and 8) and had a successful s2i build with a proxy in play.  Does that mean there was a change in these specific Tomcat images that prevented failure during the build, like the customer reports?


"Test with 
registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat8-openshift            latest              8bcae5669106        3 weeks ago         735.8 MB
registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift            latest              fb6eaa939b95        3 weeks ago         733.8 MB

build successfully under proxy"

Or did you add these xPaas environment variables?
$HTTP_PROXY_HOST
$HTTP_PROXY_PORT
$HTTP_PROXY_USERNAME
$HTTP_PROXY_PASSWORD
$HTTP_PROXY_NONPROXYHOSTS

I'm trying to determine if there is still an issue with xPaas JWS.

Hello all,

We experience the same issue for all xPaaS builds.

Maven ignores the standard HTTP_PROXY/http_proxy (uppercase/lowercase).

Is there a global workaround that can be put in place until this bug is fixed?

Thanks

@Bogdan if you're using our images, you can use the env variables described above which are respected by those images.  If you're using a random maven image, then no, there is no global workaround, you'll have to configure your maven settings in whatever way that image supports being configured.

Hello,

Yes we are using official RedHat images and the variables that you have suggested are working ok.

Thank you for the help.

I see that you have updated the documentation also: https://docs.openshift.com/enterprise/3.2/install_config/http_proxies.html#using-maven-behind-a-proxy

But the issue isn't completely solved. Is there a bug opened for xPaaS builds that are failing intermittent with "Peer not authenticated"? 

Thanks in advance

> But the issue isn't completely solved. Is there a bug opened for xPaaS builds 
> that are failing intermittent with "Peer not authenticated"? 


@Bgodan not that i'm aware of, please open it as a new bug and we'll investigate.

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