Currently when clicking Start or Stop button on a cluster instance, when loading is terminated the button is still in enabled state.
The issue is rooted in the fact that instances is continuously fetched from the backend, it's content changes, but the selectedInstances keeps a reference to the old/stale value.
For instance, if the instance in the instances array goes from status=Running to status=Stopped, this change is never reflected in the selectedInstance.
Currently when clicking Start or Stop button on a cluster instance, when loading is terminated the button is still in enabled state.
The issue is rooted in the fact that instances is continuously fetched from the backend, it's content changes, but the selectedInstances keeps a reference to the old/stale value. For instance, if the instance in the instances array goes from status=Running to status=Stopped, this change is never reflected in the selectedInstance.
Workaround
Refresh the page to see the updated button state.