-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[backend] Nested pipeline does not pass artifacts outputs #10041
Comments
similar to #10039 but with artifacts |
/assign @chensun |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/remove-lifecycle stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
I'm facing the same issue still. Was there a solution or workaround for this? |
@zetinaricky what version of Kubeflow Pipeline (backend) are you using? |
backend version is v1.8.0 |
@zetinaricky that's seems very unlikely, given this issue is about KFP v2. I assume you are using Kubeflow 1.8, which includes Kubeflow Pipelines 2.0.3? |
I'm running kubeflow 1.9 with kubeflow pipelines 2.2.0 and this is still an issue. Its concerning that code provided in documentation is broken. Kubeflow Backend Version: v1.9.0 Relevant logs of the issue:
PipelineSpec: @chensun Can this issue be reopened and frozen from getting auto closed. |
This issue appears to be redundant with #10039. |
@droctothorpe Thoughts on closing this in favor of #10039 |
I think that's a good idea 👍 . |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/close |
@droctothorpe: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi!
I was trying to run a nested pipeline, where the first pipeline outputs two artifacts (
Dataset
) and the second one consumes them. I was generally the following example from the docs as the motivation: https://www.kubeflow.org/docs/components/pipelines/v2/data-types/artifacts/#using-output-artifactsEven though the pipeline compiled successfully and in the UI it seems right, it seems like the pipeline fails (a failure sign near the run, but in the graph itself it seems like the first pipeline still running but its outputs are ready. I attached an image below), and there is no indication in the second pipeline for the failure reason.
If I look at the logs of the failing pod I see:
The UI:
Environment
I used Local deployment on kind:
and I'm using
kfp
version 2.0.1Steps to reproduce
Here's the code I've used:
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: