New error entries with 1.14.0-rc.1

[Dannhausen]

What steps did you take and what happened: We did an update to version 1.14.0-rc.1 in our developer stage. After that update we got several log entries like this: time="2024-06-14T00:44:51Z" level=error msg="error encountered while scanning stdout" backupLocation=velero/default cmd=/plugins/velero-plugin-for-aws controller=backup-sync error="read |0: file already closed" logSource="pkg/plugin/clientmgmt/process/logrus_adapter.go:90"

Our backup is running normal so far.

What did you expect to happen: No new unknown error messages

Environment:

• Velero version (use velero version): Client: Version: v1.13.2 Git commit: 4d961fb6fec384ed7f3c1b7c65c818106107f5a6 Server: Version: v1.14.0-rc.1
• Velero features (use velero client config get features): not set
• Kubernetes version (use kubectl version): Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.15+vmware.1"

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• :+1: for "I would like to see this bug fixed as soon as possible"
• :-1: for "There are more important bugs to focus on right now"

[reasonerjt]

@Dannhausen Are you using AWS S3?

[Dannhausen]

Yes, but a self hosted privat version.