This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: support disabling CreateVolume in CSI migration
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-19 14:09
Elapsed36m17s
Revision52de17e1c63f56493e47dd6bb4273284b38e8402
Refs 944

No Test Failures!


Error lines from build-log.txt

... skipping 72 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   192k      0 --:--:-- --:--:-- --:--:--  192k
Downloading https://get.helm.sh/helm-v3.6.3-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azuredisk-csi:v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a not found: manifest unknown: manifest tagged by "v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=178403f9ee73133fabf1c2048060ab45834c0b6a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-07-19T14:15:37Z -extldflags "-static""  -mod vendor -o _output/amd64/azurediskplugin.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 1541 lines ...
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'volumeSnapshotClassName is the name of the VolumeSnapshotClass
                  requested by the VolumeSnapshot. If not specified, the default snapshot
                  class will be used if one exists. If not specified, and there is
                  no default snapshot class, dynamic snapshot creation will fail.
                  Empty string is not allowed for this field. TODO(xiangqian): a webhook
                  validation on empty string. More info: https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes'
                type: string
            required:
            - source
            type: object
... skipping 22 lines ...
                  pre-existing snapshot, this field will be filled with the "creation_time"
                  value returned from the CSI "ListSnapshots" gRPC call if the driver
                  supports it. If not specified, it indicates that the creation time
                  of the snapshot is unknown.
                format: date-time
                type: string
              error:
                description: error is the last observed error during snapshot creation,
                  if any. This field could be helpful to upper level controllers(i.e.,
                  application controller) to decide whether they should continue on
                  waiting for the snapshot to be created based on the type of error
                  reported.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 10 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                x-kubernetes-int-or-string: true
            type: object
        required:
        - spec
... skipping 265 lines ...
                  supports it. If not specified, it indicates the creation time is
                  unknown. The format of this field is a Unix nanoseconds time encoded
                  as an int64. On Unix, the command `date +%s%N` returns the current
                  time in nanoseconds since 1970-01-01 00:00:00 UTC.
                format: int64
                type: integer
              error:
                description: error is the latest observed error during snapshot creation,
                  if any.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 9 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                format: int64
                minimum: 0
                type: integer
              snapshotHandle:
                description: snapshotHandle is the CSI "snapshot_id" of a snapshot
                  on the underlying storage system. If not specified, it indicates
                  that dynamic snapshot creation has either failed or it is still
                  in progress.
                type: string
            type: object
        required:
        - spec
        type: object
... skipping 819 lines ...
        - name: csi-resizer
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.1.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - '-handle-volume-inuse-error=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
... skipping 175 lines ...
Go Version: go1.16.6
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0719 14:24:07.359442   13921 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0719 14:24:07.360517   13921 azuredisk.go:211] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0719 14:24:07.362306   13921 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0719 14:24:07.362388   13921 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0719 14:24:07.362393   13921 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0719 14:24:07.362397   13921 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0719 14:24:07.362400   13921 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 16 lines ...
Jul 19 14:24:14.728: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-pw8nf] to have phase Bound
Jul 19 14:24:14.830: INFO: PersistentVolumeClaim pvc-pw8nf found and phase=Bound (101.769533ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Jul 19 14:24:15.137: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-rqv99" in namespace "azuredisk-8081" to be "Error status code"
Jul 19 14:24:15.240: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 102.37039ms
Jul 19 14:24:17.342: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204989881s
Jul 19 14:24:19.447: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309488348s
Jul 19 14:24:21.550: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 6.413151535s
Jul 19 14:24:23.653: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 8.515570817s
Jul 19 14:24:25.757: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 10.619587137s
Jul 19 14:24:27.860: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 12.722258179s
Jul 19 14:24:29.962: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 14.824539925s
Jul 19 14:24:32.066: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 16.928290579s
Jul 19 14:24:34.168: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Pending", Reason="", readiness=false. Elapsed: 19.030863211s
Jul 19 14:24:36.272: INFO: Pod "azuredisk-volume-tester-rqv99": Phase="Failed", Reason="", readiness=false. Elapsed: 21.13485479s
STEP: Saw pod failure
Jul 19 14:24:36.272: INFO: Pod "azuredisk-volume-tester-rqv99" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 19 14:24:36.408: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-rqv99"
Jul 19 14:24:36.514: INFO: Pod azuredisk-volume-tester-rqv99 has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-rqv99 in namespace azuredisk-8081
Jul 19 14:24:36.627: INFO: deleting PVC "azuredisk-8081"/"pvc-pw8nf"
... skipping 81 lines ...
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:67
    should succeed when creating a shared disk [disk.csi.azure.com][windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:138
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:158
STEP: Creating a kubernetes client
Jul 19 14:25:21.938: INFO: >>> kubeConfig: /root/tmp542858252/kubeconfig/kubeconfig.northeurope.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0719 14:25:22.448286   13921 azuredisk_driver.go:57] Using azure disk driver: disk.csi.azure.com
... skipping 19 lines ...
Jul 19 14:25:26.991: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-d9zbb] to have phase Bound
Jul 19 14:25:27.093: INFO: PersistentVolumeClaim pvc-d9zbb found and phase=Bound (101.362055ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 19 14:25:27.407: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wcq6w" in namespace "azuredisk-495" to be "Succeeded or Failed"
Jul 19 14:25:27.509: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 101.807013ms
Jul 19 14:25:29.613: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206021408s
Jul 19 14:25:31.716: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309075377s
Jul 19 14:25:33.819: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.411855715s
Jul 19 14:25:35.921: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.514179168s
Jul 19 14:25:38.024: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.61676425s
... skipping 4 lines ...
Jul 19 14:25:48.542: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 21.134849474s
Jul 19 14:25:50.646: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 23.23890493s
Jul 19 14:25:52.749: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 25.342588808s
Jul 19 14:25:54.853: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Pending", Reason="", readiness=false. Elapsed: 27.446242789s
Jul 19 14:25:56.957: INFO: Pod "azuredisk-volume-tester-wcq6w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.550384866s
STEP: Saw pod success
Jul 19 14:25:56.957: INFO: Pod "azuredisk-volume-tester-wcq6w" satisfied condition "Succeeded or Failed"
Jul 19 14:25:56.957: INFO: deleting Pod "azuredisk-495"/"azuredisk-volume-tester-wcq6w"
Jul 19 14:25:57.063: INFO: Pod azuredisk-volume-tester-wcq6w has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-wcq6w in namespace azuredisk-495
Jul 19 14:25:57.169: INFO: deleting PVC "azuredisk-495"/"pvc-d9zbb"
Jul 19 14:25:57.169: INFO: Deleting PersistentVolumeClaim "pvc-d9zbb"
... skipping 38 lines ...
Jul 19 14:26:24.653: INFO: PersistentVolumeClaim pvc-mf2kf found and phase=Bound (101.970936ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: attaching disk to node#0
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 19 14:26:38.383: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-q825j" in namespace "azuredisk-9947" to be "Succeeded or Failed"
Jul 19 14:26:38.486: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 102.98345ms
Jul 19 14:26:40.590: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206262914s
Jul 19 14:26:42.693: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309101657s
Jul 19 14:26:44.797: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.413319588s
Jul 19 14:26:46.900: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516384496s
Jul 19 14:26:49.003: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.619611017s
... skipping 8 lines ...
Jul 19 14:27:07.929: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 29.545766913s
Jul 19 14:27:10.034: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 31.650171681s
Jul 19 14:27:12.141: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 33.757882294s
Jul 19 14:27:14.245: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Pending", Reason="", readiness=false. Elapsed: 35.861531909s
Jul 19 14:27:16.349: INFO: Pod "azuredisk-volume-tester-q825j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 37.965325458s
STEP: Saw pod success
Jul 19 14:27:16.349: INFO: Pod "azuredisk-volume-tester-q825j" satisfied condition "Succeeded or Failed"
Jul 19 14:27:16.349: INFO: deleting Pod "azuredisk-9947"/"azuredisk-volume-tester-q825j"
Jul 19 14:27:16.456: INFO: Pod azuredisk-volume-tester-q825j has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-q825j in namespace azuredisk-9947
Jul 19 14:27:16.970: INFO: deleting PVC "azuredisk-9947"/"pvc-mf2kf"
Jul 19 14:27:16.970: INFO: Deleting PersistentVolumeClaim "pvc-mf2kf"
... skipping 65 lines ...
Jul 19 14:27:45.527: INFO: PersistentVolumeClaim pvc-n4zm9 found and phase=Bound (4.308594641s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 19 14:27:45.833: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v7hpp" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jul 19 14:27:45.937: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 103.46407ms
Jul 19 14:27:48.040: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206446025s
Jul 19 14:27:50.143: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.310044359s
Jul 19 14:27:52.247: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.413904339s
Jul 19 14:27:54.350: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516845921s
Jul 19 14:27:56.455: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.62144188s
Jul 19 14:27:58.561: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.72721348s
Jul 19 14:28:00.664: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.830474322s
Jul 19 14:28:02.767: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.933912206s
Jul 19 14:28:04.870: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Pending", Reason="", readiness=false. Elapsed: 19.036328673s
Jul 19 14:28:06.973: INFO: Pod "azuredisk-volume-tester-v7hpp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 21.140057627s
STEP: Saw pod success
Jul 19 14:28:06.973: INFO: Pod "azuredisk-volume-tester-v7hpp" satisfied condition "Succeeded or Failed"
Jul 19 14:28:06.974: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-v7hpp"
Jul 19 14:28:07.079: INFO: Pod azuredisk-volume-tester-v7hpp has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-v7hpp in namespace azuredisk-5356
Jul 19 14:28:07.186: INFO: deleting PVC "azuredisk-5356"/"pvc-n4zm9"
Jul 19 14:28:07.186: INFO: Deleting PersistentVolumeClaim "pvc-n4zm9"
... skipping 44 lines ...
Jul 19 14:28:53.652: INFO: PersistentVolumeClaim pvc-zn2vn found but phase is Pending instead of Bound.
Jul 19 14:28:55.756: INFO: PersistentVolumeClaim pvc-zn2vn found and phase=Bound (4.312523124s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Jul 19 14:28:56.064: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jzbvt" in namespace "azuredisk-6413" to be "Succeeded or Failed"
Jul 19 14:28:56.165: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 101.258417ms
Jul 19 14:28:58.267: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.203560952s
Jul 19 14:29:00.371: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.306628202s
Jul 19 14:29:02.474: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.410073001s
Jul 19 14:29:04.577: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.513111642s
Jul 19 14:29:06.681: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.617000333s
Jul 19 14:29:08.784: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.720105687s
Jul 19 14:29:10.888: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.823639642s
Jul 19 14:29:12.989: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.925531882s
Jul 19 14:29:15.092: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 19.028025207s
Jul 19 14:29:17.195: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Pending", Reason="", readiness=false. Elapsed: 21.13114694s
Jul 19 14:29:19.298: INFO: Pod "azuredisk-volume-tester-jzbvt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 23.234165075s
STEP: Saw pod success
Jul 19 14:29:19.299: INFO: Pod "azuredisk-volume-tester-jzbvt" satisfied condition "Succeeded or Failed"
Jul 19 14:29:19.299: INFO: deleting Pod "azuredisk-6413"/"azuredisk-volume-tester-jzbvt"
Jul 19 14:29:19.406: INFO: Pod azuredisk-volume-tester-jzbvt has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-jzbvt in namespace azuredisk-6413
Jul 19 14:29:19.517: INFO: deleting PVC "azuredisk-6413"/"pvc-zn2vn"
Jul 19 14:29:19.517: INFO: Deleting PersistentVolumeClaim "pvc-zn2vn"
... skipping 45 lines ...
Jul 19 14:30:07.760: INFO: PersistentVolumeClaim pvc-28cgj found and phase=Bound (4.309290948s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 19 14:30:08.067: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ssbjc" in namespace "azuredisk-4147" to be "Succeeded or Failed"
Jul 19 14:30:08.169: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 101.86968ms
Jul 19 14:30:10.272: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204941923s
Jul 19 14:30:12.375: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.307800856s
Jul 19 14:30:14.479: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.411959431s
Jul 19 14:30:16.582: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.515205596s
Jul 19 14:30:18.685: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.618181966s
Jul 19 14:30:20.788: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.721361444s
Jul 19 14:30:22.891: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.824268731s
Jul 19 14:30:24.995: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.928335873s
Jul 19 14:30:27.098: INFO: Pod "azuredisk-volume-tester-ssbjc": Phase="Pending", Reason="", readiness=false. Elapsed: 19.031545537s
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-07-19T14:30:27Z"}
++ early_exit_handler
++ '[' -n 178 ']'
++ kill -TERM 178
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...