This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 86
InfraTest sporadic failure on CI #2999
Comments
EnMasses's registration of custom kinds looks sounds. I'm suspicious of the coding of io.fabric8.kubernetes.internal.KubernetesDeserializer. I think the io.fabric8.kubernetes.internal.KubernetesDeserializer#MAP ought to be synchronised or CHM as it is updated at runtime by many threads. I think this will explain the sporadic absence of the key from the map. |
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 15, 2019
… issue with io.fabric8.kubernetes.internal.KubernetesDeserializer
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 16, 2019
… issue with io.fabric8.kubernetes.internal.KubernetesDeserializer
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 16, 2019
… issue with io.fabric8.kubernetes.internal.KubernetesDeserializer
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 16, 2019
… issue with io.fabric8.kubernetes.internal.KubernetesDeserializer
obabec
added a commit
to obabec/enmasse
that referenced
this issue
Jul 17, 2019
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 17, 2019
…r to address thread-safety issue. Fixes EnMasseProject#2999.
Open issue/PR against kubernetes-client https://github.com/k-wall/kubernetes-client/pull/new/issue-1634-kubernetesdeserializer-threadsafety |
k-wall
added a commit
to k-wall/enmasse
that referenced
this issue
Jul 17, 2019
…r to address thread-safety issue. Fixes EnMasseProject#2999.
k-wall
added a commit
that referenced
this issue
Jul 18, 2019
Fix #2999: Locally override io.fabric8.kubernetes.internal.KubernetesDeserializer to address thread-safety issue.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
io.enmasse.systemtest.standard.infra.InfraTest
are seen to sporadically fail on Jenkins CI with a failure like this:Looking into the api-server log, I see deserialisation errors. These deserialisation errors explain why the api-server did not know about the newly created plan.
The text was updated successfully, but these errors were encountered: