-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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] "cannot save parameter" for cached steps #10729
Comments
/assign @hbelmiro |
Hi @hbelmiro, any update on this? I bumped my company pipelines to make them compliant with KFP v2 and they are throwing these errors: time="2024-06-07T17:29:06.435Z" level=info msg="sub-process exited" argo=true error="<nil>"
time="2024-06-07T17:29:06.436Z" 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-06-07T17:29:06.436Z" 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-06-07T17:29:06.436Z" level=error msg="cannot save parameter /tmp/outputs/condition" argo=true error="open /tmp/outputs/condition: no such file or directory" |
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. |
Still relevant |
/lifecycle frozen |
(Potential solve) may not be relevant. We had similar issue in our cluster, based on Rancher Kubernetes engine 2. Applied something like this for the given Kubeflow profile namespace. apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-egress-to-ml-pipeline-controller
namespace: profile-namespace
spec:
policyTypes:
- Egress
egress:
- ports:
- port: 8887
protocol: TCP
to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kubeflow
- podSelector:
matchLabels:
app: ml-pipeline
app.kubernetes.io/name: kubeflow-pipelines This may not be fine grained enough, but you get the idea. Running recurring pipeline of say hello example: Without networkPolicy
With networkPolicy
Hope this solves the issue, for others. |
/assign |
When running a simple V2 pipeline more than once the following errors happen:
Pipeline sample:
This is related to #9678 (comment).
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: