Bug 1689263
Summary: | Internal error: Unable to set dialer for kube-service-catalog | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | szustkowski |
Component: | Service Catalog | Assignee: | Jay Boyd <jaboyd> |
Status: | CLOSED DUPLICATE | QA Contact: | Jian Zhang <jiazha> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-03-19 11:44:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
szustkowski
2019-03-15 14:24:38 UTC
This error: Error from server (InternalError): an error on the server (\"unable to set dialer for kube-service-catalog/apiserver as rest transport is of type *transport.debuggingRoundTripper\") has prevented the request from succeeding" is a pretty solid indication you are hitting the same issue described in https://bugzilla.redhat.com/show_bug.cgi?id=1680342. There is a bug in core Kubernetes (https://github.com/kubernetes/kubernetes/issues/65848) where if the verbosity level for the Kube API Server is configured >5 it will cause this error and log the error "unable to set dialer for kube-service-catalog/apiserver as rest transport is of type *transport.debuggingRoundTripper" Can you please check the configuration and verify the log level? And change loglevel < 5 if applicable? Hey Jay, thanks for your help. This was exactly the issue. I have set the loglevel to 4 (it was 6 when i opened this bugreport), and the installation succeeded. So, it is a duplicate of #1680342. Best regards, Simon Excellent, thanks Simon. *** This bug has been marked as a duplicate of bug 1680342 *** |