Bug 1680214
| Summary: | Service catalog cannot access brokers in the cluster with Multitenant | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | Networking | Assignee: | Casey Callendrello <cdc> |
| Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | aos-bugs, chezhang, dyan, jfan, zitang |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| 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-06-04 10:44:27 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
Jian Zhang
2019-02-23 04:43:30 UTC
@Jay, Based on my understanding, kube-service-catalog and kube-service-catalog-controller-manager can have different netid. But, the kube-service-catalog must have the same netid with kube-system, the kube-service-catalog-controller-manager must have the same netid with brokers. Correct me if I'm wrong. @Jian this sounds right. Certainly the pods in kube-service-catalog-controller-manager must be able to communicate with all service brokers. Understood. Can you outline exactly which namespaces need access to which? I can update the netnamespaces. Casey, The broker namespaces including: openshift-template-service-broker, openshift-ansible-service-broker Their netids should be as the same as the netid of the "kube-service-catalog-controller-manager". If possible, we can set all of them to "1", as the same as the netid of "kube-system". Additionally the pods in kube-service-catalog must be able to communicate with etcd (kube-system). The openshift-network-operator image info that the fixed PR merged in. As below:
io.openshift.build.commit.id=15204e63ace4000afa531193af95894371d4cfe0
io.openshift.build.commit.url=https://github.com/openshift/cluster-network-operator/commit/15204e63ace4000afa531193af95894371d4cfe0
io.openshift.build.source-location=https://github.com/openshift/cluster-network-operator
[jzhang@dhcp-140-18 multitenant]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.nightly-2019-02-28-054829 True False 3h49m Cluster version is 4.0.0-0.nightly-2019-02-28-054829
Check their netnamespaces, all of them is "1", looks good.
[jzhang@dhcp-140-18 multitenant]$ oc get netnamespaces
NAME NETID
kube-service-catalog 1
kube-service-catalog-controller-manager 1
kube-system 1
openshift-ansible-service-broker 1
...
openshift-template-service-broker 1
Install the ServiceCatalog and fake broker in corresponding namespaces.
[jzhang@dhcp-140-18 multitenant]$ oc get pods -n kube-service-catalog
NAME READY STATUS RESTARTS AGE
apiserver-752j7 1/1 Running 0 21m
apiserver-gtz24 1/1 Running 0 21m
apiserver-nwp6h 1/1 Running 0 21m
[jzhang@dhcp-140-18 multitenant]$ oc get pods -n kube-service-catalog-controller-manager
NAME READY STATUS RESTARTS AGE
controller-manager-d5x5m 1/1 Running 0 21m
controller-manager-fq7b4 1/1 Running 0 21m
controller-manager-pbr9c 1/1 Running 0 21m
[jzhang@dhcp-140-18 multitenant]$ oc get clusterservicebroker
NAME URL STATUS AGE
ups-broker http://ups-broker.openshift-ansible-service-broker.svc.cluster.local Ready 15m
[jzhang@dhcp-140-18 multitenant]$ oc get pods -n openshift-ansible-service-broker
NAME READY STATUS RESTARTS AGE
ups-broker-779c4fd54c-cj2tq 1/1 Running 0 15m
LGTM, verify it. Thanks!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |