You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Deployed Kubeflow Pipelines (KFP) using Kubeflow 1.9.1 Release Candidate 1.
The installation process completed successfully without any errors.
After the installation, I opened the Kubeflow dashboard.
When accessing the Kubeflow Pipelines dashboard, an error occurred.
Other components like Notebook, Volume, etc., are working fine, but the issue is specific to the KFP dashboard.
Expected result
ml-pipeline-ui error : 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
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /apis/v1beta1/healthz
GET /pipeline/
GET /pipeline/static/js/main.b980985e.js
GET /pipeline/static/css/main.e10b3034.css
GET /pipeline/system/project-id
GET /pipeline/apis/v1beta1/healthz
GET /pipeline/apis/v2beta1/pipelines?page_token=&page_size=10&sort_by=created_at%20desc&filter=
Proxied request: /apis/v2beta1/pipelines?page_token=&page_size=10&sort_by=created_at%20desc&filter=
GET /pipeline/system/cluster-name
GET /pipeline/apis/v2beta1/pipelines?namespace=kubeflow-user-example-com&page_token=&page_size=10&sort_by=created_at%20desc&filter=
Proxied request: /apis/v2beta1/pipelines?namespace=kubeflow-user-example-com&page_token=&page_size=10&sort_by=created_at%20desc&filter=
/server/node_modules/node-fetch/lib/index.js:1491
reject(new FetchError(`request to ${request.url} failed, reason: ${err.message}`, 'system', err));
^
FetchError: request to http://metadata/computeMetadata/v1/project/project-id failed, reason: getaddrinfo ENOTFOUND metadata
at ClientRequest.<anonymous> (/server/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketErrorListener (node:_http_client:501:9)
at Socket.emit (node:events:517:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ENOTFOUND',
code: 'ENOTFOUND'
}
Node.js v18.18.2
Maybe, this issue is same as #11247. In my environment, #11321 resolved this issue.
For trying this PR, I edited deployment ml-pipeline-ui as follows, and this error disappeared.
kubectl edit deployment ml-pipeline-ui -n kubeflow
# Add environment variable DISABLE_GKE_METADATA and set to true.
# spec:
# containers:
# - env:
# - name: DISABLE_GKE_METADATA
# value: "true"
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: