Skip to content
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

ML CLI issues with Kubeflow 0.5.0 in GCP #1355

Closed
ianhellstrom opened this issue May 20, 2019 · 5 comments
Closed

ML CLI issues with Kubeflow 0.5.0 in GCP #1355

ianhellstrom opened this issue May 20, 2019 · 5 comments

Comments

@ianhellstrom
Copy link

I have a Kubeflow cluster (version 0.5.0) in GCP and when I run ml pipeline list I get the following error message (with debug options):

GET /api/v1/namespaces/kube/services/ml-pipeline:8888/proxy/apis/v1beta1/pipelines?page_size=10 HTTP/1.1
Host: 104.155.13.193
User-Agent: Go-http-client/1.1
Accept: application/json
Accept-Encoding: gzip


HTTP/2.0 404 Not Found
Content-Length: 198
Audit-Id: 13e549f6-46c9-47e5-9042-bda38cb6c7ea
Content-Type: application/json
Date: Mon, 20 May 2019 07:53:19 GMT

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"services \"ml-pipeline\" not found","reason":"NotFound","details":{"name":"ml-pipeline","kind":"services"},"code":404}

Issue calling the service. Use the '--debug' flag to see the HTTP request/response. Raw error from the client: json: cannot unmarshal object into Go struct field APIStatus.details of type []*pipeline_model.ProtobufAny
Failed to list pipelines. Params: '&{Filter:<nil> PageSize:0xc00055c7d8 PageToken:<nil> SortBy:<nil> timeout:30000000000 Context:context.Background.WithDeadline(2019-05-20 09:53:54.526218 +0200 CEST m=+35.038768714 [34.867252102s]) HTTPClient:<nil>}'
github.com/kubeflow/pipelines/backend/src/common/util.NewUserError
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/common/util/error.go:121
github.com/kubeflow/pipelines/backend/src/common/client/api_server.(*PipelineClient).List
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/common/client/api_server/pipeline_client.go:168
github.com/kubeflow/pipelines/backend/src/common/client/api_server.listAllForPipeline
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/common/client/api_server/pipeline_client.go:191
github.com/kubeflow/pipelines/backend/src/common/client/api_server.(*PipelineClient).ListAll
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/common/client/api_server/pipeline_client.go:178
github.com/kubeflow/pipelines/backend/src/cmd/ml/cmd.NewPipelineListCmd.func2
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/cmd/ml/cmd/pipeline.go:175
github.com/spf13/cobra.(*Command).execute
	/Users/ian/go/src/github.com/spf13/cobra/command.go:762
github.com/spf13/cobra.(*Command).ExecuteC
	/Users/ian/go/src/github.com/spf13/cobra/command.go:850
github.com/spf13/cobra.(*Command).Execute
	/Users/ian/go/src/github.com/spf13/cobra/command.go:800
github.com/kubeflow/pipelines/backend/src/cmd/ml/cmd.(*RootCommand).Execute
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/cmd/ml/cmd/root.go:101
main.main
	/Users/ian/go/src/github.com/kubeflow/pipelines/backend/src/cmd/ml/main.go:16
runtime.main
	/usr/local/opt/go/libexec/src/runtime/proc.go:200
runtime.goexit
	/usr/local/opt/go/libexec/src/runtime/asm_amd64.s:1337

It works fine for my Kubeflow cluster that's still on version 0.4.X.

@jdelfino
Copy link

We're also hitting this.

@jdelfino
Copy link

jdelfino commented Jun 4, 2019

Adding --namespace kubeflow to the command works around this issue.

@ianhellstrom
Copy link
Author

ianhellstrom commented Jun 10, 2019

I cannot confirm that the namespace works. In my original commands I always used the namespace.

@jessiezcc
Copy link
Contributor

@IronPan, any idea?

@IronPan
Copy link
Member

IronPan commented Jul 3, 2019

The go CLI is no longer supported in 0.5. We will have a python based CLI soon.
WIP a39ae8e#diff-eae18bc41e1434dd98fa2dd989531da8

@IronPan IronPan closed this as completed Jul 3, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants