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

Executions page does not render name and state properly #3109

Closed
rafbarr opened this issue Feb 18, 2020 · 2 comments · Fixed by #3196
Closed

Executions page does not render name and state properly #3109

rafbarr opened this issue Feb 18, 2020 · 2 comments · Fixed by #3196

Comments

@rafbarr
Copy link
Contributor

rafbarr commented Feb 18, 2020

What steps did you take:

Execute the steps in the metadata demo notebook: https://github.com/kubeflow/metadata/blob/master/sdk/python/sample/demo.ipynb.

What happened:

Executions are created properly. I can query the metadata store and see that the information is there. However, the name does not get rendered correctly in the UI. As a consequence, there are no links for the executions, which means there's not a good way to accessing past executions.

Screen Shot 2020-02-18 at 3 28 24 PM

What did you expect to happen:

The name of the execution gets listed in the execution page.

Environment:

How did you deploy Kubeflow Pipelines (KFP)?

Using kfctl and https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_istio_dex.v1.0.0.yaml.

KFP version: 881cde2

KFP SDK version:

$ pip list | grep kfp
kfp                        0.2.2.1   
kfp-server-api             0.1.40

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind bug

@Bobgy
Copy link
Contributor

Bobgy commented Feb 25, 2020

Thanks for the report, I will try to reproduce

@Bobgy
Copy link
Contributor

Bobgy commented Feb 28, 2020

Okay, I reproduced the issue, digging what was wrong here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants