This step is in Error state with this message: Error (exit code 1): failed to put file: You did not provide the number of bytes specified by the Content-Length HTTP header.

[grapefruitL]

My pipeline contains several components, these components have OutputPath type variables, so there will be files stored in minio, but when running, a random component will generate an error: This step is in Error state with this message: Error (exit code 1): failed to put file: You did not provide the number of bytes specified by the Content-Length HTTP header. Sometimes Pipeline can run normally again, how is this? What's the matter?

[zijianjoy]

/assign @Linchin

It might be something related to argoworkflow: https://github.com/argoproj/argo-workflows/issues?q=is%3Aissue+%22+failed+to+put+file%22+is%3Aclosed.

[vietanhdev]

We deployed a Kubeflow system with Minio on a NFS Storage and the same error happened. It might be related to slow disk speed on Minio, or any timeout configuration? Please update if there is any news. Thank you!

[Linchin]

Hi @grapefruitL and @vietanhdev, could you provide a minimum code that will reproduce the error?

[grapefruitL]

Unfortunately it can't be reproduced and many times a retry will fix it @Linchin

[vietanhdev]

I think this issue may be due to slow disk io. The system was installed on an NFS drive <-> HDD.

[github-actions[bot]]

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.

[rimolive]

Closing this issue. No activity for more than a year.

/close

[google-oss-prow[bot]]

@rimolive: Closing this issue.

In response to this:

Closing this issue. No activity for more than a year.

/close

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.