Details
-
Bug
-
Status: On Hold
-
Low
-
Resolution: Unresolved
-
None
-
None
-
None
-
minikube v1.15.1
-
Yes
-
Yes
-
Impediment
Description
User impact:
When user tries to restart a failed cluster it will get stuck in processing and user can't see error logs in UI anymore
STR:
Go to DBaaS page and register minikube cluster
Install 1.7.0 operator
Add XtraDB cluster that will fail (too much CPU for example)
Click the "Restart" button and wait
Expected result:
DB cluster should be failed again after restart (this is how it worked with 1.6.0 operator)
PXC: 0/1 nodes are available: 1 Insufficient memory. Observed Generation: 2 Pmm: Proxysql: Ready: 3 Size: 3 Status: ready Pxc: Message: 0/1 nodes are available: 1 Insufficient memory. Ready: 1 Size: 3 Status: error State: error Events: <none>
Actual result:
DB cluster in initializing forever:
PXC: 0/1 nodes are available: 1 Insufficient memory. ProxySQL: 0/1 nodes are available: 1 Insufficient memory. Observed Generation: 2 Pmm: Proxysql: Message: 0/1 nodes are available: 1 Insufficient memory. Ready: 2 Size: 3 Status: error Pxc: Message: 0/1 nodes are available: 1 Insufficient memory. Size: 3 Status: error State: initializing Events: <none>
Attachments
Issue Links
- is caused by
-
-
- Done
-