noidname01 opened a new pull request #642: URL: https://github.com/apache/submarine/pull/642
### What is this PR for? There is a time lag between the frontend and backend of MLflow. To elaborate, the status of the button "MLflow" on the experiment page becomes clickable. However, the MLflow server has not launched, and thus when we click the button, the webpage will show "Bad gateway". Wait until the MLflow launches successfully, the button works well. ### What type of PR is it? [ Improvement ] ### Todos ### What is the Jira issue? https://issues.apache.org/jira/projects/SUBMARINE/issues/SUBMARINE-863 ### How should this be tested? ```bash # Step1 Launch the frontend # At ./submarine cd submarine-workbench/workbench-web npm install npm run start # Step2 Run Submarine and Port-Forward # At ./submarine helm install submarine ./helm-charts/submarine kubectl port-forward --address 0.0.0.0 service/submarine-traefik 32080:80 #Step3 Open the localhost:4200 to check the MLflow button is loading, and localhost:32080/mlflow is Service Unavailable #Step4 Wait for the MLflow button become clickable and check localhost:32080/mlflow again, it should display normally # If you want to test again, you can delete the pod of mlflow. ``` ### Screenshots (if appropriate) https://user-images.githubusercontent.com/55401762/124378566-9aa39c80-dce4-11eb-828d-0bf825418af3.mp4 ### Questions: * Do the license files need updating? No * Are there breaking changes for older versions? No * Does this need new documentation? No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
