Description of problem:
By mistake if template is deleted. Associated clusterserviceclass is not pointing to the correct template as template is not available. So, new template created is not pointing to the clusterserviceclass correctly and not available on the service catalog.
I tried with the workaround in such way keeping scenario such that there is no related clusterserviclass and template in OCP environment.
In this scenario if I create a new template then new clusterserviceclass is automatically generated pointing to the correct template.
But this scenario seems to be not feasible since we cannot manage the servicebinding of the currently running serviceinstance.
can we create the template for specific uid for already present clusterserviceclass?
Version-Release number of selected component (if applicable):
The newly created template is not pointing to the correct clusterserviceclass because of that deployment of the template cannot be done from service catalog.
It seems like the Template Service Broker is working as expected. There is no way for it to know if the newly created templates are equivalent to the old template.
If a template is removed there is currently no way or reassociating it back. This is not a bug.