Invalid input error: Invalid resource references for experiment. Expect one namespace type with owner relationship
See original GitHub issueI deployed kubeflow from using this kfdef (uses manifests from v1.1-branch)
When trying to run a pipeline on an external, multi-user auth cluster I’m getting a modal pop-up with this error:
The relevant parts of the JupyterLab logs seem to be:
Validate experiment request failed.: Invalid input error: Invalid resource references for experiment. Expect one namespace type with owner relationship. Got:[]","message":"Validate experiment request failed.: Invalid input error: Invalid resource references for experiment.
The full trace is in this gist.
Elyra successfully creates the pipeline, and if I then log in to the kubeflow GUI and manually create an experiment from the pipeline Elyra created, it works as expected.
I notice the same error message in a kubeflow/pipelines issue here but it seems to only apply only to applications using the in-cluster endpoint, which isn’t the case for me.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Kubeflow - error in create_run_from_pipeline_func
message":"Invalid input error: Invalid resource references for experiment. ListExperiment requires filtering by namespace.
Read more >Forcing a single team Namespace - Google Groups
While trying to use the /apis/v1beta1/experiments API point, I noticed this error: "'Invalid input error: Invalid resource references for experiment.
Read more >Runtime Configuration — Elyra 2.2.4 documentation
A runtime configuration provides Elyra access to external resources, such as Kubeflow ... Invalid input error: Invalid resource references for experiment.
Read more >Multi-user Isolation - Kubeflow Pipelines
Kubeflow Pipelines separates resources using Kubernetes namespaces ... The namespace is specified by a “resource reference” with type of ...
Read more >Descriptor Format of Catalog Entities - Backstage.io
There may be others that also develop or otherwise touch the API, but there will always be one ultimate owner. kind, Default namespace,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kevin-bates Thanks for the suggestion. I built a version of Elyra locally with my namespace hard-coded and passed into the
create_experiment
call like suggested. Unfortunately this didn’t change anything; I still get the same error. Re: cluster availability, I can provide access to the cluster for any IBMer who is willing to troubleshoot. I’m also happy to just try whatever other suggestions you have / provide information about the cluster.Thanks @akchinSTC! The docker image you provided me does fix the problem so https://github.com/elyra-ai/elyra/pull/1081 will resolve this issue.