Red Hat Bugzilla – Bug 1462086
Binding Serviceclass on overview is always keep in loading
Last modified: 2018-01-25 16:12:38 EST
Created attachment 1288271 [details]
binding icon is keep loading
Description of problem:
When service catalog is deployed but broker is not created, Create an app and a serviceclass, bind the app to serviceclass from overview, the icon is always loading, but the Binding is actually created.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use latest kubectl create serviceclass
description: A user provided service
- description: Sample plan description
2. Create an app for a project, like Perl
3. On service catalog UI console, select the serviceclass "myserviceclass" and choose the project.
4. Choose "Bind to an application" and select "myperl"
5. # kubectl get binding -n xiaocwan-t --context=service-catalog (to use latest cli)
4. Icon is always keep in loading, but the Binding is actually created (binding is pending), please see the screenshot
4. The Icon should not always be loading
1) Binding is a potentially long-lived asynchronous operation, the binding object will be created, but the binding is not yet ready / the credentials are not yet available. This is why it remains in a pending state. If you look at the binding object the conditions on it will show its not ready yet. We can consider changing the terminology from Pending to "Not ready" or something similar, but that is not a blocking issue so I am lowering the severity.
2) You should never in any valid environment create a service class directly without a backing broker. If you create the Broker it is the service catalog's responsibility to ask the broker what services it has and the catalog will create the service classes. I will talk to the service catalog folks and see if there is anything they can do to prevent this. But either way that is a separate issue.
Paul - ensure that when we create our roles that only the catalog is privileged to create service classes to avoid users attempting to do it directly.
How was the catalog deployed in this case? The rolebindings in the current installer PR will not allow ordinary users to create or update serviceclasses.
This is a negative scenario, when user create a binding without broker, the status icon is always Running and it looks like the binding is being created all the time.
The understanding is right:
The binding staying in "Pending" (or "Not Ready" if we change the terminology) is correct. The binding object has been created but is not ready yet. From the console's perspective this is the appropriate way to display this state. Leaving this open for the moment until we decide if we are changing the terminology to "Not Ready".