-
Notifications
You must be signed in to change notification settings - Fork 144
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
k8s_info openshift.dynamic.exceptions.ServiceUnavailableError: 503 #349
Comments
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves openshift#349
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves openshift#349
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves openshift#349
Hmm, I'm not sure why it would be trying to hit the endpoints that are down, unless discovery as a whole is broken because of it. It should be lazily accessing endpoints as needed,
Yes, we're discovering all the core V1 resources (ie,
The client is fully dynamic, and uses the discovery interface to discover all resources, including the core resources. This lets us handle it all very generically without needing any special casing for core resources.
Yes I'd expect that's true, though could you try? |
I am also facing a similar problem with Error is reporting:
To reproduce run below ansible in above version
Is there any solution or workaround to resolve the above issue? |
@uditgaurav This PR fixes the issue for me: #350 |
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves #349
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves openshift#349
There are situations where a given api service unrelated to the requested resource is unavailable and an ServiceUnavailableError exception is thrown. The change in this PR will allow resources to be found if the resource being requested is unrelated to an api service that is unavailable. Resolves #349 Co-authored-by: Bill Lynch <wmlynch@us.ibm.com>
Target cluster version: Openshift 4.2.5
openshift pip version: 0.10.0
kubernetes pip version: 10.0.1
ansible 2.9.2
Ansible std_error block:
Inspecting the cluster, post k8s_info failure, the following apiservices are in a failed state.
I'm surmising that one or both of the apiservices in
FailedDiscoveryCheck
caused the failure. What I'm struggling to understand is why.Some questions/observations:
v1
resources, Is this correct?oc get service -n default kubernetes -o yaml
the command would work successfully.The text was updated successfully, but these errors were encountered: