-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to build container-image via s2i in some clusters #7454
Comments
Additional information after ~5 hours, the build eventually fails, with the following logs
|
s2i-java-11 ClusterTask build (pipeline) in OCP v.4.8 ends in same failure as above: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException However, this thread reads as though the problem is fixed. I've taken the s2i-java-11 ClusterTask and made a custom Task within my project/namespace, and even added Quarkus build args:
But, it still ends in error. Please advise. |
@sbreault I think that you are mixing concepts that are not meant to be mixed together. |
I added the Quarkus args to the build task because without them I get a NPE with very little info to troubleshoot the root cause: Caused by: java.lang.NullPointerException |
STEP 4/9: USER root
|
Describe the bug
S2i binary builds fails in some clusters, with
stream was reset
andtimeout
errors.Expected behavior
S2i build should work normally.
Actual behavior
During the s2i build, which happens using the java client we receive the following excpetion:
The build then falls back to the use of the
oc
binary that sometime fails with a timeout error.To Reproduce
Steps to reproduce the behavior:
oc login --token=<some token> --server=<some server>
Configuration
The text was updated successfully, but these errors were encountered: