Bug 1584996
| Summary: | [Behindproxy]Failed to connect to maven repo when build with openshift/wildfly-101-centos7 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
| Component: | RFE | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED UPSTREAM | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.10.0 | CC: | aos-bugs, bparees, erich, jokerman, mmccomas, snalawad, wsun, wzheng |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-12 13:53:13 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
Wenjing Zheng
2018-06-01 06:22:40 UTC
did you set "HTTP_PROXY_HOST" and "HTTP_PROXY_PORT" ? those are the variables the wildfly image uses to configure its maven proxy settings. Is it possible to let wildfly image read the proxy setting in master-config? so that users don't need to define it manuallt. > Is it possible to let wildfly image read the proxy setting in master-config? so that users don't need to define it manuallt.
definitely not master-config.
The global proxy settings for builds would come from the build defaulter/overrider plugin, which, when using ansible, do automatically get configured to set the cluster proxy settings. However they still will only set HTTP_PROXY/HTTPS_PROXY, so the wildfly image won't do anything with them today.
The wildfly image would need to be updated to respect HTTP_PROXY/HTTPS_PROXY instead of(or in addition to) HTTP_PROXY_HOST/HTTP_PROXY_PORT.
I can look at making that change.
Thanks for your reply, I will change this bug to a RFE bug to track this issue, ok? Ben，whether this change only apply to openshift/wildfly-130-centos7? But openshift/wildfly-130-centos7 also failed with below error: [ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo1.maven.org/maven2): http://file.rdu.redhat.com: Name or service not known: Unknown host http://file.rdu.redhat.com: Name or service not known -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException Aborting due to error code 1 from mvn package error: build error: non-zero (13) exit code from openshift/wildfly-130-centos7@sha256:7e8d7d44402ce2a91f640e6d45563733e667a33ffc9f478b04b06d08a9e35606 Yes I only made the change in the 13.0 wildfly image. I think this is working correctly.. maven is now using your proxy as expected. However the container running maven presumably does not have access to the redhat network(or perhaps the VPN DNS settings) and thus can't resolve the proxy hostname you're using. Out proxy address has port number 3128, actually, it should use http://file.rdu.redhat.com:3128 to download package. you're getting an unknown host error, the port is irrelevant because it failed to resolve "file.rdu.redhat.com" as a valid hostname. OK, moving this bug to be verified now. |