Open jtama opened 1 month ago
I don't think they are duplicate PATCH
requests. It's just that Jib does concurrent blob uploads. I think for whatever reason, the harbor registry sometimes fails to handle concurrent uploads correctly. I guess retrying Jib in a loop or even completely disabling concurrency in Jib (slow, of course, particularly bad for first-time build and uploads) would be a workaround.
I don't think they are duplicate
PATCH
requests. It's just that Jib does concurrent blob uploads. I think for whatever reason, the harbor registry sometimes fails to handle concurrent uploads correctly. I guess retrying Jib in a loop or even disabling concurrency in Jib (slow, of course, particularly for initial uploads) would be a workaround.
Hi @chanseokoh ... I think this looks like the problem we have too. I could not find howto "disable concurrency" in Jib.
@ddittmar to disable Jib concurrency, set the system property jib.serialize
to false
, like -Djib.serialize=false
on the command line. See this example. Note it's a system property only; no Maven or Gradle configuration for this Jib system property.
Environment:
Description of the issue: During our ci pipeline, we have an error occuring randomly. Jib triggers the same patch request which generates an error.
We know that the first patch takes a bit long to (1m12s) successfully process, but in the mean time Jib sends a second patch requests. This second request is the one that generates an error.
Expected behavior:
Should ends up fine.
Steps to reproduce:
Unable to reproduce surely the error.
Log output:
Additional Information: The registry is a privately managed harbor