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
Error Not Handled by K8s Module #112
Comments
Hello I want to add, I am also getting this error
Run from : local/outside of cluster What i've noticed is that after 30 mins I get this error. Therefore, k8 module were successful in executing the podScenarios before. I've ran twice, the first run errored out after about 30 mins with 2 successful podScenario executions. The second run errored out about after 40 mins with 3 successful podScenario executions. Kubernetes cluster used is IKS (Ibm cloud Kubernetes Service) |
that's also my suspicion |
Thank you for the reports! I think this issue is related to token expiration in From reading kubernetes-client/python#741, I see that a fix was merged to support the refresh in OpenAPITools/openapi-generator#3594. Some PR's from projects that implement this refresh technique: apache/airflow#5731 and DataBiosphere/toil#2869. |
@seeker89, can you label this issue? |
Reading through kubernetes-client/python#741 I understand that |
This seems to be more of a brute force solution to the problem DataBiosphere/toil#2869 but I guess it would move us forward too. |
The next major release (kubernetes-client/python#1124) of K8s Python client should fix this issue. |
Still waiting for the next major release. We can track it here: kubernetes-client/python#1052 |
Error return from call to k8s api not handled...e.g.:
NOTE: this is a flakey cluster, that sometimes returns this error. Not a consistent error from kubernetes.
Analysis: Logging error...missing handler
The text was updated successfully, but these errors were encountered: