Description of problem: 1. Cluster upgraded from 3.6 to 3.7 successfully. 2. While running service_catalog.yml, its failing all the time on the same task TASK [ansible_service_broker : Create the Broker resource in the catalog] "msg": { "cmd": "/usr/bin/oc create -f /tmp/brokerout-** -n default", "results": {}, "returncode": 1, "stderr": "Error from server (Forbidden): error when creating \"/tmp/brokerout-**\": clusterservicebrokers.servicecatalog.k8s.io \"ansible-service-broker\" is forbidden: not yet ready to handle request\n", "stdout": "" } 3. POD's are up and running in both openshift-ansible-service-catalog & kube-service-catalog namespaces. But openshift-template-service-broker namespace is not present yet due to the incomplete installation of service_catalog. 4. There was a similar Bugzilla[1] which has been closed with an errata. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1523625
Would you please provide: - The logs from the apiserver pod in kube-service-catalog ns - The output of `oc get apiservices servicecatalog.k8s.io/v1beta1 -o yaml` Thanks!
I have requested the yaml from the customer and provided the logs to the bz
Still looking for output from `oc get apiservices servicecatalog.k8s.io/v1beta1 -o yaml`. Also, I see both the Catalog API Server and Catalog Controller Manager pods are in a crash loop backoff. Please also provide output of `oc describe` on both pods in the kube-service-catalog namespace. Thanks.
$ oc get apiservices/v1beta1.servicecatalog.k8s.io -o yaml apiVersion: apiregistration.k8s.io/v1beta1 kind: APIService metadata: creationTimestamp: 2018-05-15T12:42:48Z name: v1beta1.servicecatalog.k8s.io resourceVersion: "108270012" selfLink: /apis/apiregistration.k8s.io/v1beta1/apiservices/v1beta1.servicecatalog.k8s.io uid: 790165d3-583d-11e8-93f5-005056b7703f spec: caBundle: .....= group: servicecatalog.k8s.io groupPriorityMinimum: 20 service: name: apiserver namespace: kube-service-catalog version: v1beta1 versionPriority: 10 status: conditions: - lastTransitionTime: 2018-05-22T13:04:16Z message: all checks passed reason: Passed status: "True" type: Available Customer is attempting a redeploy of the service catalog. If this fails we will provide latest requested info.
closing, we can't reproduce, looks to be environmental
I'm going to close out this BZ again per comment #16. Please open a new issue if you continue to have problems.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days