Open omriel1 opened 1 year ago
similar to https://github.com/kubeflow/pipelines/issues/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 Kubeflow pipelines Version: 2.2.0 Kubeflow pipelines SDK: 2.8.0
Relevant logs of the issue:
I0808 00:48:51.435502 15 driver.go:252] parent DAG: id:96 name:"run/abb87731-e26c-4d9b-9d58-3be8d07fd5fe" type_id:13 type:"system.DAGExecution" last_known_state:RUNNING custom_properties:{key:"display_name" value:{string_value:""}} custom_properties:{key:"inputs" value:{struct_value:{fields:{key:"a" value:{number_value:3.2}} fields:{key:"b" value:{number_value:9.2}}}}} custom_properties:{key:"task_name" value:{string_value:""}} create_time_since_epoch:1723078026064 last_update_time_since_epoch:1723078026064
I0808 00:48:51.877802 15 driver.go:926] parent DAG input parameters: map[a:number_value:3.2 b:number_value:9.2], artifacts: map[]
F0808 00:48:52.134460 15 main.go:79] KFP driver: driver.Container(pipelineName=pythagorean, runID=abb87731-e26c-4d9b-9d58-3be8d07fd5fe, task="square-root", component="comp-square-root", dagExecutionID=96, componentSpec) failed: failed to resolve inputs: resolving input parameter x with spec task_output_parameter:{producer_task:"square-and-sum" output_parameter_key:"Output"}: cannot find output parameter key "Output" in producer task "square-and-sum"
time="2024-08-08T00:48:52.832Z" level=info msg="sub-process exited" argo=true error="<nil>"
time="2024-08-08T00:48:52.832Z" level=error msg="cannot save parameter /tmp/outputs/pod-spec-patch" argo=true error="open /tmp/outputs/pod-spec-patch: no such file or directory"
time="2024-08-08T00:48:52.832Z" level=error msg="cannot save parameter /tmp/outputs/cached-decision" argo=true error="open /tmp/outputs/cached-decision: no such file or directory"
time="2024-08-08T00:48:52.832Z" level=error msg="cannot save parameter /tmp/outputs/condition" argo=true error="open /tmp/outputs/condition: no such file or directory"
Error: exit status 1
PipelineSpec: pipeline_in_pipeline_spec.txt
@chensun Can this issue be reopened and frozen from getting auto closed.
This issue appears to be redundant with https://github.com/kubeflow/pipelines/issues/10039.
@droctothorpe Thoughts on closing this in favor of #10039
I think that's a good idea 👍 .
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 👍.