Description of problem: When describe serviceinstance, some error events show "ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil>". It's better to add more details for these errors. Version-Release number of selected component (if applicable): openshift v3.9.0-0.47.0 kubernetes v1.9.1+a0ce1bc657 How reproducible: always Steps to Reproduce: 1.Describe a serviceinstance 2. 3. Actual results: some error events show "ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil>" Warning ErrorWithParameters 3m service-catalog-controller-manager failed to prepare parameters nil: secrets "mysql-ephemeral-parameters4alxx" not found Normal Provisioning 3m service-catalog-controller-manager The instance is being provisioned asynchronously Warning ProvisionCallFailed 3m service-catalog-controller-manager Error provisioning ServiceInstance of ClusterServiceClass (K8S: "5028e5a5-1776-11e8-b8ae-fa163e82662b" ExternalName: "mysql-ephemeral") at ClusterServiceBroker "template-service-broker": Status: 409; ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil> Warning ClusterServiceBrokerReturnedFailure 3m service-catalog-controller-manager Error provisioning ServiceInstance of ClusterServiceClass (K8S: "5028e5a5-1776-11e8-b8ae-fa163e82662b" ExternalName: "mysql-ephemeral") at ClusterServiceBroker "template-service-broker": Status: 409; ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil> Normal ProvisionedSuccessfully 2m service-catalog-controller-manager The instance was provisioned successfully Expected results: It's better to add more details for these errors. Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1507429
This text is generated from the information the broker returns, so there's no information we can add to this in the catalog - the broker has to send it. For that reason, I'm closing this as NOTABUG - let me know if there are any questions.
Alternatively file this bug against Template Service Broker (or Ansible Service Broker)... The 409 indicates a conflict, my guess is Catalog sent multiple provision requests to the broker and the broker doesn't like that but that is really a guess.
@Jay So do you plan to fix the conflict error?
we plant to fix the cause of the conflict error. See https://bugzilla.redhat.com/show_bug.cgi?id=1567847