This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: create snapshot on external resource group failure
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-09-09 13:37
Elapsed39m27s
Revisiond37b5e335a424ebb7c422421078f6848701812ad
Refs 532

No Test Failures!


Error lines from build-log.txt

... skipping 61 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11213  100 11213    0     0   115k      0 --:--:-- --:--:-- --:--:--  115k
Downloading https://get.helm.sh/helm-v3.3.1-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:e2e-35f35defd2eafed8c9d75641ee57880267c525f7 || make azuredisk-container push
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:e2e-35f35defd2eafed8c9d75641ee57880267c525f7 not found: manifest unknown: manifest tagged by "e2e-35f35defd2eafed8c9d75641ee57880267c525f7" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=linux go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=e2e-35f35defd2eafed8c9d75641ee57880267c525f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=35f35defd2eafed8c9d75641ee57880267c525f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2020-09-09T13:44:49Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.topologyKey=topology.disk.csi.azure.com/zone -extldflags "-static"" -o _output/azurediskplugin ./pkg/azurediskplugin
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=e2e-35f35defd2eafed8c9d75641ee57880267c525f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=35f35defd2eafed8c9d75641ee57880267c525f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2020-09-09T13:45:56Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.topologyKey=topology.disk.csi.azure.com/zone -extldflags "-static"" -o _output/azurediskplugin.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
no builder "container-builder" found
docker buildx create --use --name=container-builder
... skipping 686 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 ...
                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 12 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 267 lines ...
                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
  version: v1beta1
... skipping 987 lines ...
Go Version: go1.15
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
W0909 13:54:23.153402   12589 azure_config.go:52] Failed to get cloud-config from secret: failed to get secret azure-cloud-provider: secrets "azure-cloud-provider" not found, skip initializing from secret
I0909 13:54:23.154259   12589 azuredisk.go:110] disable UseInstanceMetadata for controller
I0909 13:54:23.155264   12589 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0909 13:54:23.155299   12589 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0909 13:54:23.155305   12589 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0909 13:54:23.155312   12589 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0909 13:54:23.155318   12589 driver.go:80] Enabling controller service capability: CLONE_VOLUME
... skipping 13 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 13:54:25.018: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-smkpv" in namespace "azuredisk-8287" to be "Succeeded or Failed"
Sep  9 13:54:25.050: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 32.143489ms
Sep  9 13:54:27.084: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066140378s
Sep  9 13:54:29.118: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099802509s
Sep  9 13:54:31.156: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137893766s
Sep  9 13:54:33.189: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171597864s
Sep  9 13:54:35.224: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206143942s
... skipping 2 lines ...
Sep  9 13:54:41.327: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.30971777s
Sep  9 13:54:43.361: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.343630111s
Sep  9 13:54:45.395: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.37736821s
Sep  9 13:54:47.429: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.411327815s
Sep  9 13:54:49.463: INFO: Pod "azuredisk-volume-tester-smkpv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.445266755s
STEP: Saw pod success
Sep  9 13:54:49.463: INFO: Pod "azuredisk-volume-tester-smkpv" satisfied condition "Succeeded or Failed"
Sep  9 13:54:49.463: INFO: deleting Pod "azuredisk-8287"/"azuredisk-volume-tester-smkpv"
Sep  9 13:54:49.558: INFO: Pod azuredisk-volume-tester-smkpv has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-smkpv in namespace azuredisk-8287
STEP: validating provisioned PV
STEP: checking the PV
... skipping 43 lines ...
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
Sep  9 13:55:55.788: INFO: deleting Pod "azuredisk-631"/"azuredisk-volume-tester-jqvbs"
Sep  9 13:55:55.823: INFO: Error getting logs for pod azuredisk-volume-tester-jqvbs: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-jqvbs)
STEP: Deleting pod azuredisk-volume-tester-jqvbs in namespace azuredisk-631
STEP: validating provisioned PV
STEP: checking the PV
Sep  9 13:55:55.922: INFO: deleting PVC "azuredisk-631"/"pvc-rp724"
Sep  9 13:55:55.922: INFO: Deleting PersistentVolumeClaim "pvc-rp724"
STEP: waiting for claim's PV "pvc-4f261bf6-61a8-4d0a-bfea-690e378b39b0" to be deleted
... skipping 40 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 13:56:48.042: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nmn7d" in namespace "azuredisk-1485" to be "Succeeded or Failed"
Sep  9 13:56:48.079: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 37.552624ms
Sep  9 13:56:50.113: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07118101s
Sep  9 13:56:52.148: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106121457s
Sep  9 13:56:54.182: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140166815s
Sep  9 13:56:56.216: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.174447125s
Sep  9 13:56:58.250: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208040433s
Sep  9 13:57:00.283: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.24122046s
Sep  9 13:57:02.317: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 14.275647061s
Sep  9 13:57:04.352: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 16.310239009s
Sep  9 13:57:06.387: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 18.345376044s
Sep  9 13:57:08.420: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Pending", Reason="", readiness=false. Elapsed: 20.378682404s
Sep  9 13:57:10.456: INFO: Pod "azuredisk-volume-tester-nmn7d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.414010069s
STEP: Saw pod success
Sep  9 13:57:10.456: INFO: Pod "azuredisk-volume-tester-nmn7d" satisfied condition "Succeeded or Failed"
Sep  9 13:57:10.456: INFO: deleting Pod "azuredisk-1485"/"azuredisk-volume-tester-nmn7d"
Sep  9 13:57:10.491: INFO: Pod azuredisk-volume-tester-nmn7d has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-nmn7d in namespace azuredisk-1485
STEP: validating provisioned PV
STEP: checking the PV
... skipping 41 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Sep  9 13:57:52.657: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-x2vv2" in namespace "azuredisk-5026" to be "Error status code"
Sep  9 13:57:52.690: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.692671ms
Sep  9 13:57:54.724: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066479434s
Sep  9 13:57:56.758: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100902864s
Sep  9 13:57:58.792: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.134734788s
Sep  9 13:58:00.825: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168329871s
Sep  9 13:58:02.859: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201983743s
Sep  9 13:58:04.892: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.234876621s
Sep  9 13:58:06.926: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.268600041s
Sep  9 13:58:08.960: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.303096489s
Sep  9 13:58:10.994: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.336476632s
Sep  9 13:58:13.028: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.370703628s
Sep  9 13:58:15.061: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.403787335s
Sep  9 13:58:17.094: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Pending", Reason="", readiness=false. Elapsed: 24.436566695s
Sep  9 13:58:19.128: INFO: Pod "azuredisk-volume-tester-x2vv2": Phase="Failed", Reason="", readiness=false. Elapsed: 26.470701914s
STEP: Saw pod failure
Sep  9 13:58:19.128: INFO: Pod "azuredisk-volume-tester-x2vv2" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Sep  9 13:58:19.163: INFO: deleting Pod "azuredisk-5026"/"azuredisk-volume-tester-x2vv2"
Sep  9 13:58:19.198: INFO: Pod azuredisk-volume-tester-x2vv2 has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-x2vv2 in namespace azuredisk-5026
STEP: validating provisioned PV
... skipping 345 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 14:06:29.805: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bpf9f" in namespace "azuredisk-5746" to be "Succeeded or Failed"
Sep  9 14:06:29.838: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 33.191207ms
Sep  9 14:06:31.872: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067873141s
Sep  9 14:06:33.906: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101801625s
Sep  9 14:06:35.940: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135694146s
Sep  9 14:06:37.975: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170161669s
Sep  9 14:06:40.009: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20446634s
... skipping 2 lines ...
Sep  9 14:06:46.114: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 16.309199269s
Sep  9 14:06:48.149: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 18.344511808s
Sep  9 14:06:50.184: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 20.379037112s
Sep  9 14:06:52.218: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Pending", Reason="", readiness=false. Elapsed: 22.413220956s
Sep  9 14:06:54.253: INFO: Pod "azuredisk-volume-tester-bpf9f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.448480731s
STEP: Saw pod success
Sep  9 14:06:54.253: INFO: Pod "azuredisk-volume-tester-bpf9f" satisfied condition "Succeeded or Failed"
STEP: cloning existing volume
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying a second pod with cloned volume
STEP: checking that the pod's command exits with no error
Sep  9 14:06:54.323: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-n784t" in namespace "azuredisk-5746" to be "Succeeded or Failed"
Sep  9 14:06:54.357: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 33.779975ms
Sep  9 14:06:56.391: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067595857s
Sep  9 14:06:58.426: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102567709s
Sep  9 14:07:00.460: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137065474s
Sep  9 14:07:02.495: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.17159922s
Sep  9 14:07:04.531: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.207303967s
... skipping 9 lines ...
Sep  9 14:07:24.889: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 30.565719421s
Sep  9 14:07:26.923: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 32.599575766s
Sep  9 14:07:28.956: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 34.633077823s
Sep  9 14:07:30.991: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Pending", Reason="", readiness=false. Elapsed: 36.667567131s
Sep  9 14:07:33.025: INFO: Pod "azuredisk-volume-tester-n784t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.701810794s
STEP: Saw pod success
Sep  9 14:07:33.025: INFO: Pod "azuredisk-volume-tester-n784t" satisfied condition "Succeeded or Failed"
Sep  9 14:07:33.025: INFO: deleting Pod "azuredisk-5746"/"azuredisk-volume-tester-n784t"
Sep  9 14:07:33.087: INFO: Pod azuredisk-volume-tester-n784t has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-n784t in namespace azuredisk-5746
STEP: validating provisioned PV
STEP: checking the PV
... skipping 65 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 14:08:25.575: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nd2x4" in namespace "azuredisk-1563" to be "Succeeded or Failed"
Sep  9 14:08:25.607: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.276906ms
Sep  9 14:08:27.641: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065973595s
Sep  9 14:08:29.675: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100040613s
Sep  9 14:08:31.710: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.134772607s
Sep  9 14:08:33.745: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170386933s
Sep  9 14:08:35.779: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204054781s
... skipping 11 lines ...
Sep  9 14:09:00.187: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 34.61202145s
Sep  9 14:09:02.224: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 36.648849166s
Sep  9 14:09:04.258: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 38.682741203s
Sep  9 14:09:06.293: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Pending", Reason="", readiness=false. Elapsed: 40.717979246s
Sep  9 14:09:08.327: INFO: Pod "azuredisk-volume-tester-nd2x4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.75231737s
STEP: Saw pod success
Sep  9 14:09:08.327: INFO: Pod "azuredisk-volume-tester-nd2x4" satisfied condition "Succeeded or Failed"
Sep  9 14:09:08.327: INFO: deleting Pod "azuredisk-1563"/"azuredisk-volume-tester-nd2x4"
Sep  9 14:09:08.364: INFO: Pod azuredisk-volume-tester-nd2x4 has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-nd2x4 in namespace azuredisk-1563
... skipping 78 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 14:10:43.051: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mhnmj" in namespace "azuredisk-4376" to be "Succeeded or Failed"
Sep  9 14:10:43.086: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.405999ms
Sep  9 14:10:45.122: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070785452s
Sep  9 14:10:47.159: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107945962s
Sep  9 14:10:49.194: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.142805393s
Sep  9 14:10:51.229: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.177953107s
Sep  9 14:10:53.271: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.219344928s
... skipping 9 lines ...
Sep  9 14:11:13.622: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.570398288s
Sep  9 14:11:15.657: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 32.605387461s
Sep  9 14:11:17.691: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.639716641s
Sep  9 14:11:19.726: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Pending", Reason="", readiness=false. Elapsed: 36.674251532s
Sep  9 14:11:21.761: INFO: Pod "azuredisk-volume-tester-mhnmj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.709104389s
STEP: Saw pod success
Sep  9 14:11:21.761: INFO: Pod "azuredisk-volume-tester-mhnmj" satisfied condition "Succeeded or Failed"
Sep  9 14:11:21.761: INFO: deleting Pod "azuredisk-4376"/"azuredisk-volume-tester-mhnmj"
Sep  9 14:11:21.875: INFO: Pod azuredisk-volume-tester-mhnmj has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.055887 seconds, 1.7GB/s
hello world

... skipping 55 lines ...
Sep  9 14:12:14.391: INFO: >>> kubeConfig: /root/tmp649945685/kubeconfig/kubeconfig.eastus2.json
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 14:12:14.501: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5zrqs" in namespace "azuredisk-9002" to be "Succeeded or Failed"
Sep  9 14:12:14.535: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 33.628577ms
Sep  9 14:12:16.569: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067421424s
Sep  9 14:12:18.603: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101654901s
Sep  9 14:12:20.637: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135505734s
Sep  9 14:12:22.671: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170114614s
Sep  9 14:12:24.706: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204792128s
... skipping 3 lines ...
Sep  9 14:12:32.842: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 18.340867179s
Sep  9 14:12:34.877: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 20.376008273s
Sep  9 14:12:36.912: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 22.411223834s
Sep  9 14:12:38.947: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Pending", Reason="", readiness=false. Elapsed: 24.44583028s
Sep  9 14:12:40.981: INFO: Pod "azuredisk-volume-tester-5zrqs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.479684652s
STEP: Saw pod success
Sep  9 14:12:40.981: INFO: Pod "azuredisk-volume-tester-5zrqs" satisfied condition "Succeeded or Failed"
STEP: creating volume snapshot class
STEP: setting up the VolumeSnapshotClass
STEP: creating a VolumeSnapshotClass
STEP: taking snapshots
STEP: creating a VolumeSnapshot for pvc-5nhl7
STEP: waiting for VolumeSnapshot to be ready to use - volume-snapshot-d846f
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying a second pod with a volume restored from the snapshot
STEP: checking that the pod's command exits with no error
Sep  9 14:13:26.213: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bhzgh" in namespace "azuredisk-9002" to be "Succeeded or Failed"
Sep  9 14:13:26.246: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 33.39823ms
Sep  9 14:13:28.280: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067583852s
Sep  9 14:13:30.314: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101461063s
Sep  9 14:13:32.349: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136229516s
Sep  9 14:13:34.383: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170045602s
Sep  9 14:13:36.417: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204715876s
... skipping 2 lines ...
Sep  9 14:13:42.524: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.311696019s
Sep  9 14:13:44.559: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.346380626s
Sep  9 14:13:46.593: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 20.380502813s
Sep  9 14:13:48.627: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Pending", Reason="", readiness=false. Elapsed: 22.41480115s
Sep  9 14:13:50.662: INFO: Pod "azuredisk-volume-tester-bhzgh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.449448119s
STEP: Saw pod success
Sep  9 14:13:50.662: INFO: Pod "azuredisk-volume-tester-bhzgh" satisfied condition "Succeeded or Failed"
Sep  9 14:13:50.662: INFO: deleting Pod "azuredisk-9002"/"azuredisk-volume-tester-bhzgh"
Sep  9 14:13:50.753: INFO: Pod azuredisk-volume-tester-bhzgh has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-bhzgh in namespace azuredisk-9002
STEP: validating provisioned PV
STEP: checking the PV
... skipping 65 lines ...
STEP: creating a PVC
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep  9 14:14:43.775: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ffgg8" in namespace "azuredisk-9718" to be "Succeeded or Failed"
Sep  9 14:14:43.812: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 36.976375ms
Sep  9 14:14:45.848: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072841953s
Sep  9 14:14:47.882: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106668654s
Sep  9 14:14:49.916: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.141433427s
Sep  9 14:14:51.951: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175640513s
Sep  9 14:14:53.984: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208918334s
... skipping 15 lines ...
Sep  9 14:15:26.537: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 42.762046234s
Sep  9 14:15:28.570: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 44.795557943s
Sep  9 14:15:30.605: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 46.830097622s
Sep  9 14:15:32.640: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Pending", Reason="", readiness=false. Elapsed: 48.864610972s
Sep  9 14:15:34.673: INFO: Pod "azuredisk-volume-tester-ffgg8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.898436106s
STEP: Saw pod success
Sep  9 14:15:34.673: INFO: Pod "azuredisk-volume-tester-ffgg8" satisfied condition "Succeeded or Failed"
Sep  9 14:15:34.673: INFO: deleting Pod "azuredisk-9718"/"azuredisk-volume-tester-ffgg8"
Sep  9 14:15:34.709: INFO: Pod azuredisk-volume-tester-ffgg8 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-ffgg8 in namespace azuredisk-9718
STEP: validating provisioned PV
STEP: checking the PV
... skipping 23 lines ...
STEP: checking the PV
Sep  9 14:16:45.510: INFO: deleting PVC "azuredisk-9718"/"pvc-ck5q8"
Sep  9 14:16:45.510: INFO: Deleting PersistentVolumeClaim "pvc-ck5q8"
STEP: waiting for claim's PV "pvc-8a0d24b5-e14c-4028-8e70-d16de00ed0c8" to be deleted
Sep  9 14:16:45.547: INFO: Waiting up to 10m0s for PersistentVolume pvc-8a0d24b5-e14c-4028-8e70-d16de00ed0c8 to get deleted
Sep  9 14:16:45.579: INFO: PersistentVolume pvc-8a0d24b5-e14c-4028-8e70-d16de00ed0c8 found and phase=Released (32.336095ms)
{"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":"2020-09-09T14:16:50Z"}