[ https://issues.apache.org/jira/browse/FLINK-11971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hequn Cheng reassigned FLINK-11971: ----------------------------------- Assignee: Hequn Cheng > Fix `Command: start_kubernetes_if_not_ruunning failed` error > ------------------------------------------------------------ > > Key: FLINK-11971 > URL: https://issues.apache.org/jira/browse/FLINK-11971 > Project: Flink > Issue Type: Bug > Components: Tests > Affects Versions: 1.8.0, 1.9.0 > Reporter: sunjincheng > Assignee: Hequn Cheng > Priority: Major > Attachments: screenshot-1.png > > > When I did the end-to-end test under Mac OS, I found the following two > problems: > 1. The verification returned for different `minikube status` is not enough > for the robustness. The strings returned by different versions of different > platforms are different. the following misjudgment is caused: > When the `Command: start_kubernetes_if_not_ruunning failed` error occurs, > the `minikube` has actually started successfully. The core reason is that > there is a bug in the `test_kubernetes_embedded_job.sh` script. The error > message as follows: > !image-2019-03-20-14-02-29-636.png! > !image-2019-03-20-14-04-17-933.png! > > {code:java} > Current check logic: echo ${status} | grep -q "minikube: Running cluster: > Running kubectl: Correctly Configured" > ==== My local messae==== > jinchengsunjcs-iMac:flink-1.8.0 jincheng$ minikube status > host: Running > kubelet: Running > apiserver: Running > kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.101{code} > So, I think we should improve the check logic of `minikube status`, What do > you think? -- This message was sent by Atlassian JIRA (v7.6.3#76005)