Bug 1662560
Summary: | service catalog apiserver fails with etcd failed reason withheld | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Steven Walter <stwalter> |
Component: | Service Catalog | Assignee: | Jay Boyd <jaboyd> |
Status: | CLOSED NOTABUG | QA Contact: | Jian Zhang <jiazha> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0.0 | CC: | rhowe, schoudha, stwalter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-02 17:45:39 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
Steven Walter
2018-12-30 00:33:18 UTC
Pods were crashing due to livenessprobe not working, but we removed probes so that the pods wouldn't crash. Steven, Could you help provide us the exact version info of the service catalog? And the cluster version. You can do the following command to get the service catalog version: $oc exec xxx(pod name) -- service-catalog --version Is this after an upgrade or a new deployment? Please provide version details. Closing this bug, this is not an issue with the service catalog. The issue that a 3rd party network sdn plugin is being used and due to that the kube-proxy is never started. The service catalog is failing because it is making call to the kubernetes service IP that should get NATd to the the masterIP. These nat rules never get setup because the kubeproxy is not running on this host. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |