Triggering s2i binary builds sometimes fails with stream was reset
#2032
Comments
|
@rhuss: If I remember correctly, we've seen this issue before on FMP and it was then when we added |
|
@iocanel oh, the good old times ;-) Yes, I remember we had a similar issue but I can't really remember the cause or fix :(. I think it could be a myriad of errors, hidden by a bad error message. For one of those errors causing this message, e.g. see https://issues.redhat.com/browse/ENTESB-8791 |
|
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
…abric8io#2032) + Add BuildConfig's name and namespace in query parameters in order to align with `oc` + Use BufferedInputStream while uploading archive file to sink. + Add recent events to exception message and some logging in case of upload failure of archive file
…abric8io#2032) + Add BuildConfig's name and namespace in query parameters in order to align with `oc` + Use BufferedInputStream while uploading archive file to sink. + Add recent events to exception message and some logging in case of upload failure of archive file
…abric8io#2032) + Add BuildConfig's name and namespace in query parameters in order to align with `oc` + Use BufferedInputStream while uploading archive file to sink. + Add recent events to exception message and some logging in case of upload failure of archive file
…abric8io#2032) + Add BuildConfig's name and namespace in query parameters in order to align with `oc` + Use BufferedInputStream while uploading archive file to sink. + Add recent events to exception message and some logging in case of upload failure of archive file
…2032) + Add BuildConfig's name and namespace in query parameters in order to align with `oc` + Use BufferedInputStream while uploading archive file to sink. + Add recent events to exception message and some logging in case of upload failure of archive file
|
Shall we close this? PR with supposedly improved error handling seems to be merged. |
Using
4.7.0version of the client.In some cases the following code:
Seems to trigger the following error:
The error seems to happen often in certain clusters, while others seem completely unaffected.
The same code run perfrectly fine in some clusters:
-v4.3
-v4.4
while in some others it didn't:
-v3.11
-v4.2
So, I am thinking that its more like an environment issue rather a version issue.
Important: In some cases falling back to
oc start-build --from-archivedoes seem to work. While in other casesocit fails with a timeout error. So, there seems to be some room of improvement here.Summing up the tasks needed for this one:
oc.Issue has been originally reported at: quarkusio/quarkus#7454
The text was updated successfully, but these errors were encountered: