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
How did you deploy Kubeflow Pipelines (KFP)?
On Amazon EKS
KFP version:
2.3.0
Steps to reproduce
Display Pipelines List.
Expected result
Pipeline List should be displayed.
Materials and Reference
GET /system/cluster-name
GET /apis/v1beta1/healthz
GET /system/project-id
GET /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 /static/favicon.ico
/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/instance/attributes/cluster-name failed, reason: getaddrinfo ENOTFOUND metadata
at ClientRequest. (/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
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Environment
On Amazon EKS
2.3.0
Steps to reproduce
Display Pipelines List.
Expected result
Pipeline List should be displayed.
Materials and Reference
GET /system/cluster-name
GET /apis/v1beta1/healthz
GET /system/project-id
GET /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 /static/favicon.ico
/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/instance/attributes/cluster-name failed, reason: getaddrinfo ENOTFOUND metadata
at ClientRequest. (/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
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: