Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
None
-
1
Description
Service Broker requires installation of service catalog on the cluster before we can create service-broker services on it.
Service Catalog is deprecated on Openshift 4.x+ : https://docs.openshift.com/container-platform/4.3/applications/service_brokers/installing-service-catalog.html
So QE went ahead and tried to install service catalog through helm, however this methodology to install Service catalog applies for kubernetes and not Openshift.
Hence it started giving off containercreatingerror , Prateek checked it on both OC clusters.
error:
Normal AddedInterface 3m18s multus Add eth0 [10.129.2.104/23]
|
Normal Pulled 3m14s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 953.269721ms
|
Warning Failed 3m2s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:25:11Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulled 3m1s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 962.563084ms
|
Warning Failed 2m50s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:25:24Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulled 2m48s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 992.808747ms
|
Warning Failed 2m36s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:25:37Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: "
|
Normal Pulled 2m23s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 944.383004ms
|
Warning Failed 2m16s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:25:58Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulled 2m4s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 930.513208ms
|
Warning Failed 118s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:26:16Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulled 106s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 1.018914521s
|
Warning Failed 100s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:26:34Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulled 87s kubelet, ip-172-31-133-122.us-west-2.compute.internal Successfully pulled image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0" in 991.52772ms
|
Warning Failed 80s kubelet, ip-172-31-133-122.us-west-2.compute.internal Error: container create failed: time="2020-12-04T14:26:54Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
|
Normal Pulling 69s (x8 over 3m15s) kubelet, ip-172-31-133-122.us-west-2.compute.internal Pulling image "quay.io/kubernetes-service-catalog/service-catalog:v0.3.0"
|
Prateeks-MacBook-Pro:couchbase-service-broker-openshift prateekkumar$ oc get pods
|
NAME READY STATUS RESTARTS AGE
|
catalog-catalog-controller-manager-7cc5877bf4-csgxg 0/1 CrashLoopBackOff 2 5m47s
|
catalog-catalog-webhook-7dd588b999-vrqcp 0/1 CreateContainerError 0 5m47s
|
couchbase-operator-admission-868ccdc9d7-f9sg7 1/1 Running 0 5h20m
|
Prateeks-MacBook-Pro:couchbase-service-broker-openshift prateekkumar$ oc get pods
|
NAME READY STATUS RESTARTS AGE
|
catalog-catalog-controller-manager-7cc5877bf4-csgxg 0/1 CrashLoopBackOff 3 12m
|
catalog-catalog-webhook-7dd588b999-vrqcp 0/1 CreateContainerError 0 12m
|
couchbase-operator-admission-868ccdc9d7-f9sg7 1/1 Running 0 5h27m
|
This could also be a permission error but it’s highly unlikely since QE is trying to run something which is kubernetes supported.
Attachments
Issue Links
- blocks
-
K8S-1639 Service Broker testing
- Resolved