azuredisk-csi-driver icon indicating copy to clipboard operation
azuredisk-csi-driver copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Azuredisk multiVolume e2e tests fail in Windows nodepools

Open mauriciopoppe opened this issue 3 years ago • 3 comments

How to reproduce it: Multivolume tests are failing in Windows with this ginkgo focus: External.Storage.*multiVolume, for example:

Summarizing 3 Failures:

[Fail] External Storage [Driver: disk.csi.azure.com] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] [It] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:662

[Fail] External Storage [Driver: disk.csi.azure.com] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] [It] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:662

[Fail] External Storage [Driver: disk.csi.azure.com] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] [It] should access to two volumes with different volume mode and retain data across pod recreation on the same node
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:662

A similar error is shown in all 3:

External Storage [Driver: disk.csi.azure.com] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  should access to two volumes with different volume mode and retain data across pod recreation on the same node
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:207
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow]
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
STEP: Creating a kubernetes client
May  6 22:32:04.209: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
STEP: Building a namespace api object, basename multivolume
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
[It] should access to two volumes with different volume mode and retain data across pod recreation on the same node
  /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:207
May  6 22:32:05.235: INFO: Creating resource for dynamic PV
May  6 22:32:05.235: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(disk.csi.azure.com) supported size:{ 1Mi}
STEP: creating a StorageClass multivolume-1673-e2e-scj84h9
STEP: creating a claim
May  6 22:32:05.497: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
May  6 22:32:05.825: INFO: Creating resource for dynamic PV
May  6 22:32:05.825: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(disk.csi.azure.com) supported size:{ 1Mi}
STEP: creating a StorageClass multivolume-1673-e2e-sczmtkg
STEP: creating a claim
STEP: Creating pod on {Name: Selector:map[] Affinity:nil} with multiple volumes
STEP: Checking if the volume1 exists as expected volume mode (Filesystem)
May  6 22:32:50.655: INFO: ExecWithOptions {Command:[/bin/sh -c test -d /mnt/volume1] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:50.655: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:50.656: INFO: ExecWithOptions: Clientset creation
May  6 22:32:50.656: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=test+-d+%2Fmnt%2Fvolume1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:32:51.709: INFO: ExecWithOptions {Command:[/bin/sh -c test -b /mnt/volume1] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:51.709: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:51.710: INFO: ExecWithOptions: Clientset creation
May  6 22:32:51.710: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=test+-b+%2Fmnt%2Fvolume1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if write to the volume1 works properly
May  6 22:32:52.534: INFO: ExecWithOptions {Command:[/bin/sh -c echo vozxy5E6Yuz5Hx7RzHCdjkVu4Pc3X0T+0O9kjZIokqOut1aKsZ65ZMS/Tk5h1KZ9ReaE5tHrih+aJvdyLkAh1g== | base64 -d | sha256sum] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:52.534: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:52.535: INFO: ExecWithOptions: Clientset creation
May  6 22:32:52.535: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=echo+vozxy5E6Yuz5Hx7RzHCdjkVu4Pc3X0T%2B0O9kjZIokqOut1aKsZ65ZMS%2FTk5h1KZ9ReaE5tHrih%2BaJvdyLkAh1g%3D%3D+%7C+base64+-d+%7C+sha256sum&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:32:54.091: INFO: ExecWithOptions {Command:[/bin/sh -c echo vozxy5E6Yuz5Hx7RzHCdjkVu4Pc3X0T+0O9kjZIokqOut1aKsZ65ZMS/Tk5h1KZ9ReaE5tHrih+aJvdyLkAh1g== | base64 -d | dd of=/mnt/volume1/file1.txt  bs=64 count=1] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:54.091: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:54.092: INFO: ExecWithOptions: Clientset creation
May  6 22:32:54.092: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=echo+vozxy5E6Yuz5Hx7RzHCdjkVu4Pc3X0T%2B0O9kjZIokqOut1aKsZ65ZMS%2FTk5h1KZ9ReaE5tHrih%2BaJvdyLkAh1g%3D%3D+%7C+base64+-d+%7C+dd+of%3D%2Fmnt%2Fvolume1%2Ffile1.txt++bs%3D64+count%3D1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if read from the volume1 works properly
May  6 22:32:54.903: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume1/file1.txt  bs=64 count=1 | sha256sum] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:54.903: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:54.904: INFO: ExecWithOptions: Clientset creation
May  6 22:32:54.904: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume1%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:32:55.637: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume1/file1.txt  bs=64 count=1 | sha256sum | grep -Fq 20fa58eb193a5e029b820c0cd9c07d84c4f7e31c47da1e3a78fdfd8b9882eaf2] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:55.637: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:55.638: INFO: ExecWithOptions: Clientset creation
May  6 22:32:55.638: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume1%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum+%7C+grep+-Fq+20fa58eb193a5e029b820c0cd9c07d84c4f7e31c47da1e3a78fdfd8b9882eaf2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if the volume2 exists as expected volume mode (Filesystem)
May  6 22:32:56.510: INFO: ExecWithOptions {Command:[/bin/sh -c test -d /mnt/volume2] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:56.510: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:56.512: INFO: ExecWithOptions: Clientset creation
May  6 22:32:56.512: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=test+-d+%2Fmnt%2Fvolume2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:32:57.245: INFO: ExecWithOptions {Command:[/bin/sh -c test -b /mnt/volume2] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:57.245: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:57.246: INFO: ExecWithOptions: Clientset creation
May  6 22:32:57.246: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=test+-b+%2Fmnt%2Fvolume2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if write to the volume2 works properly
May  6 22:32:57.905: INFO: ExecWithOptions {Command:[/bin/sh -c echo FNaGIlOzURXW5Lwq4gDR57sUBd30XDN0TxHb3gx5AeEYWJOMJY2LwbxOqbgJCcFS/YJ/1b3LX5dY5ip1bTmlNQ== | base64 -d | sha256sum] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:57.905: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:57.906: INFO: ExecWithOptions: Clientset creation
May  6 22:32:57.906: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=echo+FNaGIlOzURXW5Lwq4gDR57sUBd30XDN0TxHb3gx5AeEYWJOMJY2LwbxOqbgJCcFS%2FYJ%2F1b3LX5dY5ip1bTmlNQ%3D%3D+%7C+base64+-d+%7C+sha256sum&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:32:58.637: INFO: ExecWithOptions {Command:[/bin/sh -c echo FNaGIlOzURXW5Lwq4gDR57sUBd30XDN0TxHb3gx5AeEYWJOMJY2LwbxOqbgJCcFS/YJ/1b3LX5dY5ip1bTmlNQ== | base64 -d | dd of=/mnt/volume2/file1.txt  bs=64 count=1] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:58.637: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:58.638: INFO: ExecWithOptions: Clientset creation
May  6 22:32:58.638: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=echo+FNaGIlOzURXW5Lwq4gDR57sUBd30XDN0TxHb3gx5AeEYWJOMJY2LwbxOqbgJCcFS%2FYJ%2F1b3LX5dY5ip1bTmlNQ%3D%3D+%7C+base64+-d+%7C+dd+of%3D%2Fmnt%2Fvolume2%2Ffile1.txt++bs%3D64+count%3D1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if read from the volume2 works properly
May  6 22:32:59.381: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume2/file1.txt  bs=64 count=1 | sha256sum] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:32:59.381: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:32:59.383: INFO: ExecWithOptions: Clientset creation
May  6 22:32:59.383: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume2%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:33:00.109: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume2/file1.txt  bs=64 count=1 | sha256sum | grep -Fq 98e6fc8a51681508f1e0fdb4daadfcd945d148aad44edfa730066b1a9ef7453c] Namespace:multivolume-1673 PodName:pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:33:00.109: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:33:00.110: INFO: ExecWithOptions: Clientset creation
May  6 22:33:00.110: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume2%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum+%7C+grep+-Fq+98e6fc8a51681508f1e0fdb4daadfcd945d148aad44edfa730066b1a9ef7453c&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:33:00.989: INFO: Deleting pod "pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80" in namespace "multivolume-1673"
May  6 22:33:01.132: INFO: Wait up to 5m0s for pod "pod-d8c4a7eb-e8c0-485a-a3f1-73c7f946be80" to be fully deleted
STEP: Creating pod on {Name: Selector:map[] Affinity:&Affinity{NodeAffinity:&NodeAffinity{RequiredDuringSchedulingIgnoredDuringExecution:&NodeSelector{NodeSelectorTerms:[]NodeSelectorTerm{NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{},MatchFields:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:metadata.name,Operator:In,Values:[weenn6plx000000],},},},},},PreferredDuringSchedulingIgnoredDuringExecution:[]PreferredSchedulingTerm{},},PodAffinity:nil,PodAntiAffinity:nil,}} with multiple volumes
STEP: Checking if the volume1 exists as expected volume mode (Filesystem)
May  6 22:33:51.656: INFO: ExecWithOptions {Command:[/bin/sh -c test -d /mnt/volume1] Namespace:multivolume-1673 PodName:pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:33:51.656: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:33:51.657: INFO: ExecWithOptions: Clientset creation
May  6 22:33:51.657: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea/exec?command=%2Fbin%2Fsh&command=-c&command=test+-d+%2Fmnt%2Fvolume1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:33:52.493: INFO: ExecWithOptions {Command:[/bin/sh -c test -b /mnt/volume1] Namespace:multivolume-1673 PodName:pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:33:52.493: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:33:52.494: INFO: ExecWithOptions: Clientset creation
May  6 22:33:52.494: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea/exec?command=%2Fbin%2Fsh&command=-c&command=test+-b+%2Fmnt%2Fvolume1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
STEP: Checking if read from the volume1 works properly
May  6 22:33:53.329: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume1/file1.txt  bs=64 count=1 | sha256sum] Namespace:multivolume-1673 PodName:pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:33:53.329: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:33:53.331: INFO: ExecWithOptions: Clientset creation
May  6 22:33:53.331: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume1%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:33:54.118: INFO: ExecWithOptions {Command:[/bin/sh -c dd if=/mnt/volume1/file1.txt  bs=64 count=1 | sha256sum | grep -Fq 20fa58eb193a5e029b820c0cd9c07d84c4f7e31c47da1e3a78fdfd8b9882eaf2] Namespace:multivolume-1673 PodName:pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
May  6 22:33:54.118: INFO: >>> kubeConfig: /usr/local/google/home/mauriciopoppe/.kube/config
May  6 22:33:54.120: INFO: ExecWithOptions: Clientset creation
May  6 22:33:54.120: INFO: ExecWithOptions: execute(POST https://10.0.1.5/api/v1/namespaces/multivolume-1673/pods/pod-46745c38-4e24-47d5-9c35-3fc75b3de0ea/exec?command=%2Fbin%2Fsh&command=-c&command=dd+if%3D%2Fmnt%2Fvolume1%2Ffile1.txt++bs%3D64+count%3D1+%7C+sha256sum+%7C+grep+-Fq+20fa58eb193a5e029b820c0cd9c07d84c4f7e31c47da1e3a78fdfd8b9882eaf2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING))
May  6 22:33:54.991: FAIL: "dd if=/mnt/volume1/file1.txt  bs=64 count=1 | sha256sum | grep -Fq 20fa58eb193a5e029b820c0cd9c07d84c4f7e31c47da1e3a78fdfd8b9882eaf2" should succeed, but failed with error message "command terminated with exit code 1"
stdout:
stderr: dd: can't open '/mnt/volume1/file1.txt': No such file or directory
Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "command terminated with exit code 1",
        },
        Code: 1,
    }
    command terminated with exit code 1
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/framework/volume.VerifyExecInPodSucceed(0x722d49f, 0x33, {0xc000c62090, 0x83})
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:662 +0x34d
k8s.io/kubernetes/test/e2e/storage/utils.CheckReadFromPath(0xc0029d2b10, 0x31, {0xc0030f2890, 0x0}, 0x0, {0xc00425acf0, 0xc004026100}, 0x7a11748, 0xc000140008)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/utils.go:547 +0x325
k8s.io/kubernetes/test/e2e/storage/testsuites.testAccessMultipleVolumes(0xc002d85ce0, {0x7b442b0, 0xc0016ef980}, {0xc0030f2260, 0x10}, {{0x0, 0x245dbf4}, 0x0, 0xc0040029c0}, {0xc0032e8890, ...}, ...)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:507 +0x6b9
k8s.io/kubernetes/test/e2e/storage/testsuites.TestAccessMultipleVolumesAcrossPodRecreation(0x711bd3b, {0x7b442b0, 0xc0016ef980}, {0xc0030f2260, 0x10}, {{0x0, 0x0}, 0x0, 0xc0040029c0}, {0xc0032e8890, ...}, ...)
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:546 +0x7ec
k8s.io/kubernetes/test/e2e/storage/testsuites.(*multiVolumeTestSuite).DefineTests.func5()
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:237 +0x465
k8s.io/kubernetes/test/e2e.RunE2ETests(0x24e2677)
        _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697
k8s.io/kubernetes/test/e2e.TestE2E(0x2456919)
        _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19
testing.tRunner(0xc000583ba0, 0x73a1f18)
        /usr/local/go/src/testing/testing.go:1259 +0x102
created by testing.(*T).Run
        /usr/local/go/src/testing/testing.go:1306 +0x35a

Is there an output log for tests that run in Windows? I tried to follow https://github.com/kubernetes-sigs/azuredisk-csi-driver/blob/master/test/external-e2e/run.sh and https://github.com/kubernetes-sigs/azuredisk-csi-driver/blob/master/test/e2e/README.md as well as reading the makefile

Environment:

  • CSI Driver version: 1.11.0
  • Kubernetes version (use kubectl version): v1.22.8
  • Containerd version: 1.5.11

mauriciopoppe avatar May 06 '22 21:05 mauriciopoppe

this command dd if=/mnt/volume1/file1.txt is not valid on Windows

andyzhangx avatar May 08 '22 11:05 andyzhangx

I think agnhost can do that, if you see the entire log you'll see other executions of dd that completed successfully

mauriciopoppe avatar May 09 '22 14:05 mauriciopoppe

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Aug 07 '22 15:08 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Sep 06 '22 15:09 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-triage-robot avatar Oct 06 '22 16:10 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

k8s-ci-robot avatar Oct 06 '22 16:10 k8s-ci-robot