-
Notifications
You must be signed in to change notification settings - Fork 96
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
Jenkins master mismatch java version with builders (java 21.0.5 vs 21.0.4) causing java.io.StreamCorruptedException: invalid stream header #9444
Comments
I don't know what got it started But it's the Jenkins client code failing, which means you'll need your team to help figure it out... |
This suggest communication issues between builder and master |
for now seems to be happening more often in artifact pipeline: |
Similar problem happens not on the checkout but the stream in long-running CI jobs. It is 100% failure.
Ci job as an example: https://jenkins.scylladb.com/job/scylla-staging/job/valerii/job/vp-longevity-aws-custom-d2-workload1-multidc-big/17/console I consider this bug as serious that should be investigated and fixed ASAP |
The builder probably got killed, the question is why, and by whom. |
It is stable behavior, all my long running jenkins jobs fail this way. Probably, some cleanup logic somewhere got changed and now cleans up builders without any regards to utilization of it. |
looking in AWS the build was stopped after the error occurred in your job
so it's not a builder that died so the next theories
so I would start by changing it for this region to stop sharing the builders |
Just saw the same error today in
Found similar issue opened 11 days ago @fruch - could it be related to java version on the builders? Is it updated automatically? BTW, the current version of java on Jenkins server is 21.0.5 , it was updated as well from the last time
|
no it's not getting auto updates the java version on the SCT builders is
|
base on our differences in version and the ones reported in stackoverflow I can bet this change might be the cause:
can we downgrade the java version on jenkins master ? |
We can't downgrade Java back to version 11, cause we already upgraded Jenkins server to version 2.488 - where Java version 11 is not supported and in addition java 11 reached end of life. We can downgrade to Java 17 - but I'm not sure it will help. Will it help to downgrade Java version to 21.0.4? |
I did meant to downgrade to that one, not to 11 I think those new HTTP limit aren't aligned between builder and master, and might be the root cause |
@fruch - seems that openjdk-21.0.4 is not available in the repository. The available versions are:
I checked current java version on all our nodes/agents:
|
If one of those builders is using multiple excecuters ? |
Our nodes, no. |
|
give it a go with job known to reproduce it: |
|
can we scan the /var/lib/jenkins/jobs folder for occurence of it, so we can track it after apply changes ? can we downgrade java to 21.0.3 ? |
Java on Jenkins server was downgraded to version to
I scanned the |
cause of issue cause by missmatch of java version between master and sct builder, we are building a new sct runner image that has up-to-date java version Ref: scylladb#9444
started the process of updating the SCT builders in: |
I've run into it again: so we might be barking the wrong tree, i.e. it's not the java version, but something else... |
I'll move forward with upgrade of the jvm on the builder side I'll limit SCT builder to 1 executer, for the time being. |
ok, let me know once you done. I will update the server side as well |
Seen multiple times today, https://jenkins.scylladb.com/job/scylla-master/job/artifacts/job/artifacts-azure-image-test/696/ and https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci-offline-installer/23/
Failed during checkout:
The text was updated successfully, but these errors were encountered: