You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When framework deploys service to openshift which fails for some reason, FW then tries to collect evidence from OCP. But if that fails too, original exception is lost (happnes somewhere here).
Happened to me, when FW tried to collect logs from pod, but the pods was deleted in a meantime. In that case I got just error
... io.fabric8.kubernetes.client.KubernetesClientException ... Pod not found...
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.requestFailure(OperationSupport.java:660)
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.requestFailure(OperationSupport.java:640)
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.assertResponseCode(OperationSupport.java:589)
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handleRaw(OperationSupport.java:739)
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handleRawGet(OperationSupport.java:474)
at io.fabric8.kubernetes.client.dsl.internal.core.v1.PodOperationsImpl.doGetLog(PodOperationsImpl.java:133)
at io.fabric8.kubernetes.client.dsl.internal.core.v1.PodOperationsImpl.getLog(PodOperationsImpl.java:141)
at io.quarkus.test.bootstrap.inject.OpenShiftClient.logs(OpenShiftClient.java:441)
at io.quarkus.test.bootstrap.OpenShiftExtensionBootstrap.printPodLogs(OpenShiftExtensionBootstrap.java:89)
at io.quarkus.test.bootstrap.OpenShiftExtensionBootstrap.onError(OpenShiftExtensionBootstrap.java:76)
at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.lambda$scenarioOnError$11(QuarkusScenarioBootstrap.java:195)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.scenarioOnError(QuarkusScenarioBootstrap.java:195)
at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.launchService(QuarkusScenarioBootstrap.java:186)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.beforeAll(QuarkusScenarioBootstrap.java:73)
at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.beforeAll(QuarkusScenarioBootstrap.java:50)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Original failure that resource failed to start was completely lost. Problem in searching for pod was, that pod was app pods restarted (rescaled 1->0->1) in that time.
Kind of related to this - why is FW deploying pods to OCP is way that that it:
Creates the deployment - which is doomed to fail, because no image is present yet
Builds the image
"Restarts" the deployment - scales it down to 0 and back up to 1.
On other places we do it in a way that it first builds the image and then deploys app on first try. That saves a lot of trouble with rescaling the pods.
The text was updated successfully, but these errors were encountered:
michalvavrik
changed the title
Framework cowers nested failures on openshift
Framework covers nested failures on openshift
Nov 14, 2024
When framework deploys service to openshift which fails for some reason, FW then tries to collect evidence from OCP. But if that fails too, original exception is lost (happnes somewhere here).
Happened to me, when FW tried to collect logs from pod, but the pods was deleted in a meantime. In that case I got just error
Original failure that resource failed to start was completely lost. Problem in searching for pod was, that pod was app pods restarted (rescaled 1->0->1) in that time.
Kind of related to this - why is FW deploying pods to OCP is way that that it:
On other places we do it in a way that it first builds the image and then deploys app on first try. That saves a lot of trouble with rescaling the pods.
The text was updated successfully, but these errors were encountered: