Details
-
Bug
-
Status: On Hold
-
Medium
-
Resolution: Unresolved
-
None
-
None
-
None
-
Yes
-
Yes
-
Yes
-
No
Description
User impact:
User is able to see and use an enabled option to create a DB cluster while the kubernetes cluster is still in provisioning state.
Steps to reproduce:
- To reproduce a K8s cluster that has operators installed but its state is still "Provisioning" (This is how it did for me, there might other scenarios to reproduce this)
- Create an EKS cluster
- Register it to a PMM instance
- Unregister it from that PMM instance
- Register the same EKS cluster to another PMM instance after two or three days
- Create a DB cluster on that EKS cluster:
- Register a fresh minikube or EKS cluster that gets resgistered successfully with operators installed and state being active.
- Click "Create DB cluster" option against that active cluster.
- In the "Create DB Cluster" window, select that EKS cluster (one that is in provisioning state) from the drop-down menu "Kubernetes Cluster"
- Create a DB cluster by filling in other required options
Actual result:
On "Create DB Cluster" window, it lets you select any kubernetes cluster even if the cluster is in provisioning state.
Expected result:
If the kubernetes cluster is in provisioning state, it should not be visible anywhere for DB cluster creation or any other relatable/similar option.