You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, the E2E tests fail because it cannot find the cleanup job log:
Dumping csi-azuredisk-controller-cleanup-h4649_kube-system_delete-azvolume-fc3da582c1cec6b959c8f48dff04068c950d22401788af7c2fbbfcbc4523d49c.log
cat: /var/log/containers/csi-azuredisk-controller-cleanup-h4649_kube-system_delete-azvolume-fc3da582c1cec6b959c8f48dff04068c950d22401788af7c2fbbfcbc4523d49c.log: No such file or directory
command terminated with exit code 1
What you expected to happen:
Tests should succeed regardless of whether this log exists.
How to reproduce it:
Anything else we need to know?:
Environment:
CSI Driver version:
Kubernetes version (use kubectl version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
What happened:
Occasionally, the E2E tests fail because it cannot find the cleanup job log:
What you expected to happen:
Tests should succeed regardless of whether this log exists.
How to reproduce it:
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: