-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[frontend] Error on Kubeflow Pipelines Dashboard: 'No Healthy Upstream', '503 UC upstream_reset_before_response_started{connection_termination}' #11260
Comments
@ChaeSeungJi We have just released https://github.com/kubeflow/manifests/releases/tag/v1.9.1-rc.2. Can you take a look and see if this release fixes your issue? |
I have the same error in v1.9.1-rc.2. Environment:
After running a pipeline from Jupyter Notebook and clicking the link the following error occurs. And, when clicking the menu |
Maybe, this issue is same as #11247. In my environment, #11321 resolved this issue.
|
@utsumi-fj thank you!!! it works good |
…ubeflow#11260 Signed-off-by: Dave Canton <[email protected]>
…ubeflow#11260 Signed-off-by: Dave Canton <[email protected]>
…ubeflow#11260 Signed-off-by: Dave Canton <[email protected]>
Environment
How did you deploy Kubeflow Pipelines (KFP)?
while ! kustomize build example | kubectl delete -f -; do echo "Retrying to delete resources"; sleep 20; done
KFP version: 1.19.1
Kubernetes version
Steps to reproduce
Other components like Notebook, Volume, etc., are working fine, but the issue is specific to the KFP dashboard.
Expected result
Error: failed to retrieve list of pipelines. Click Details for more information.
Details :
An error occurred upstream connect error or disconnect/reset before headers. reset reason: remote connection failure, transport failure reason: delayed connect error: 111
When refreshing the page (F5), the following screen appears:
no healthy upstream
Materials and Reference
What I've Tried
kubeflow/kubeflow#5561
#4469
kubeflow/kubeflow#5271
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: