This job view page is being replaced by Spyglass soon. Check out the new job view.
PRedreed: feat: Azure Disk CSI Driver V2 (a.k.a. Project Mandalay) initial implementation
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-05-26 22:49
Elapsed55m17s
Revisiona4d0729f5e638b725bfcfb54797cb12b9eff3e49
Refs 864

No Test Failures!


Error lines from build-log.txt

... skipping 69 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   219k      0 --:--:-- --:--:-- --:--:--  219k
Downloading https://get.helm.sh/helm-v3.5.4-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:v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7" 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=v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-05-26T22:56:08Z -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"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.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 1223 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7" 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.schedulerVersion=v2.0.0-alpha.1-b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=b21ff9e66fdd8ad12cc37a23ff1b69fdb2cee0d7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-05-26T23:04:03Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -extldflags "-static"" -mod vendor -o _output/amd64/azdiskschedulerextender.exe ./pkg/azdiskschedulerextender
docker buildx rm container-builder || true
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
... skipping 1583 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 227 lines ...
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              Nil status indicates that the underlying volume of AzVolumeAttachment
              has not yet been attached to the specified node
            properties:
              error:
                description: Error occured during attach/detach of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 197 lines ...
            - volumeCapability
            type: object
          status:
            description: status represents the current state of AzVolume. Nil status
              indicates that the underlying volume has not yet been provisioned
            properties:
              error:
                description: Error occured during creation/deletion of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 995 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 239 lines ...
Go Version: go1.16.4
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0526 23:10:43.651790   14449 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0526 23:10:43.652614   14449 azuredisk.go:191] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0526 23:10:43.652800   14449 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0526 23:10:43.652814   14449 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0526 23:10:43.652818   14449 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0526 23:10:43.652823   14449 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0526 23:10:43.652827   14449 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
May 26 23:10:44.967: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b9bnw" in namespace "azuredisk-8081" to be "Succeeded or Failed"
May 26 23:10:45.000: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 33.092797ms
May 26 23:10:47.034: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066791514s
May 26 23:10:49.071: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104328534s
May 26 23:10:51.105: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137956503s
May 26 23:10:53.140: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.172697476s
May 26 23:10:55.175: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208518258s
... skipping 9 lines ...
May 26 23:11:15.526: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.55923165s
May 26 23:11:17.563: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.596071508s
May 26 23:11:19.598: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 34.631308606s
May 26 23:11:21.633: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Pending", Reason="", readiness=false. Elapsed: 36.666583815s
May 26 23:11:23.669: INFO: Pod "azuredisk-volume-tester-b9bnw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.702556993s
STEP: Saw pod success
May 26 23:11:23.670: INFO: Pod "azuredisk-volume-tester-b9bnw" satisfied condition "Succeeded or Failed"
May 26 23:11:23.670: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-b9bnw"
May 26 23:11:23.770: INFO: Pod azuredisk-volume-tester-b9bnw has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-b9bnw in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 40 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
May 26 23:12:24.526: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-825x5"
May 26 23:12:24.563: INFO: Error getting logs for pod azuredisk-volume-tester-825x5: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-825x5)
STEP: Deleting pod azuredisk-volume-tester-825x5 in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
May 26 23:12:24.670: INFO: deleting PVC "azuredisk-1318"/"pvc-5zksl"
May 26 23:12:24.670: INFO: Deleting PersistentVolumeClaim "pvc-5zksl"
STEP: waiting for claim's PV "pvc-d2dbffb1-0789-4b76-add7-ad935da3e509" to be deleted
... skipping 37 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
May 26 23:13:11.265: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wfvmb" in namespace "azuredisk-694" to be "Succeeded or Failed"
May 26 23:13:11.302: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 37.180106ms
May 26 23:13:13.336: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070860929s
May 26 23:13:15.370: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104844879s
May 26 23:13:17.404: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139558585s
May 26 23:13:19.438: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173509526s
May 26 23:13:21.473: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208043648s
... skipping 2 lines ...
May 26 23:13:27.578: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.313647097s
May 26 23:13:29.614: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.34894774s
May 26 23:13:31.649: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.384764815s
May 26 23:13:33.684: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.419744512s
May 26 23:13:35.719: INFO: Pod "azuredisk-volume-tester-wfvmb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.454139019s
STEP: Saw pod success
May 26 23:13:35.719: INFO: Pod "azuredisk-volume-tester-wfvmb" satisfied condition "Succeeded or Failed"
May 26 23:13:35.719: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-wfvmb"
May 26 23:13:35.755: INFO: Pod azuredisk-volume-tester-wfvmb has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-wfvmb in namespace azuredisk-694
STEP: validating provisioned PV
STEP: checking the PV
... skipping 38 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
May 26 23:14:12.474: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-dc6vn" in namespace "azuredisk-3274" to be "Error status code"
May 26 23:14:12.508: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 34.375468ms
May 26 23:14:14.543: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069430119s
May 26 23:14:16.578: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10417384s
May 26 23:14:18.612: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138091153s
May 26 23:14:20.646: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.172322152s
May 26 23:14:22.682: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.207719053s
May 26 23:14:24.716: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.241949252s
May 26 23:14:26.750: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.275900741s
May 26 23:14:28.786: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.312202292s
May 26 23:14:30.822: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 18.348587567s
May 26 23:14:32.859: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 20.385108755s
May 26 23:14:34.893: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 22.418746911s
May 26 23:14:36.928: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Pending", Reason="", readiness=false. Elapsed: 24.454254388s
May 26 23:14:38.964: INFO: Pod "azuredisk-volume-tester-dc6vn": Phase="Failed", Reason="", readiness=false. Elapsed: 26.490395093s
STEP: Saw pod failure
May 26 23:14:38.964: INFO: Pod "azuredisk-volume-tester-dc6vn" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May 26 23:14:39.002: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-dc6vn"
May 26 23:14:39.039: INFO: Pod azuredisk-volume-tester-dc6vn has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-dc6vn in namespace azuredisk-3274
STEP: validating provisioned PV
... skipping 336 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
May 26 23:22:51.540: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wzrl7" in namespace "azuredisk-3090" to be "Succeeded or Failed"
May 26 23:22:51.573: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.944104ms
May 26 23:22:53.606: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066620848s
May 26 23:22:55.641: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10096812s
May 26 23:22:57.676: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13610801s
May 26 23:22:59.710: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169854729s
May 26 23:23:01.745: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.205192735s
... skipping 2 lines ...
May 26 23:23:07.856: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.31637346s
May 26 23:23:09.891: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 18.350910222s
May 26 23:23:11.928: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 20.388456322s
May 26 23:23:13.963: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Pending", Reason="", readiness=false. Elapsed: 22.423463657s
May 26 23:23:15.999: INFO: Pod "azuredisk-volume-tester-wzrl7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.458959888s
STEP: Saw pod success
May 26 23:23:15.999: INFO: Pod "azuredisk-volume-tester-wzrl7" 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
May 26 23:23:16.139: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jvk6q" in namespace "azuredisk-3090" to be "Succeeded or Failed"
May 26 23:23:16.172: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 33.517905ms
May 26 23:23:18.206: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067412853s
May 26 23:23:20.247: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108134803s
May 26 23:23:22.283: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.144558326s
May 26 23:23:24.368: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.229695006s
May 26 23:23:26.402: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.262992785s
... skipping 10 lines ...
May 26 23:23:48.780: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 32.641460047s
May 26 23:23:50.815: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 34.676770655s
May 26 23:23:52.851: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 36.712492905s
May 26 23:23:54.887: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Pending", Reason="", readiness=false. Elapsed: 38.74824353s
May 26 23:23:56.921: INFO: Pod "azuredisk-volume-tester-jvk6q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.782771029s
STEP: Saw pod success
May 26 23:23:56.921: INFO: Pod "azuredisk-volume-tester-jvk6q" satisfied condition "Succeeded or Failed"
May 26 23:23:56.921: INFO: deleting Pod "azuredisk-3090"/"azuredisk-volume-tester-jvk6q"
May 26 23:23:57.035: INFO: Pod azuredisk-volume-tester-jvk6q has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-jvk6q in namespace azuredisk-3090
STEP: validating provisioned PV
STEP: checking the PV
... skipping 52 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
May 26 23:24:44.069: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jn7qr" in namespace "azuredisk-4078" to be "Succeeded or Failed"
May 26 23:24:44.102: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 33.347668ms
May 26 23:24:46.136: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06737894s
May 26 23:24:48.178: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109226621s
May 26 23:24:50.215: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.145860096s
May 26 23:24:52.250: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.180612435s
May 26 23:24:54.286: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216751057s
... skipping 2 lines ...
May 26 23:25:00.389: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.320028296s
May 26 23:25:02.424: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.35489363s
May 26 23:25:04.459: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.390162208s
May 26 23:25:06.494: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.42466483s
May 26 23:25:08.528: INFO: Pod "azuredisk-volume-tester-jn7qr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.458888977s
STEP: Saw pod success
May 26 23:25:08.528: INFO: Pod "azuredisk-volume-tester-jn7qr" 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
May 26 23:25:08.670: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-84jx5" in namespace "azuredisk-4078" to be "Succeeded or Failed"
May 26 23:25:08.705: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 35.381517ms
May 26 23:25:10.740: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07008378s
May 26 23:25:12.776: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10625288s
May 26 23:25:14.811: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140796433s
May 26 23:25:16.846: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175740358s
May 26 23:25:18.881: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.210809563s
... skipping 2 lines ...
May 26 23:25:24.988: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.318169276s
May 26 23:25:27.023: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.353261242s
May 26 23:25:29.058: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.388327053s
May 26 23:25:31.095: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.424940282s
May 26 23:25:33.129: INFO: Pod "azuredisk-volume-tester-84jx5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.458729431s
STEP: Saw pod success
May 26 23:25:33.129: INFO: Pod "azuredisk-volume-tester-84jx5" satisfied condition "Succeeded or Failed"
May 26 23:25:33.129: INFO: deleting Pod "azuredisk-4078"/"azuredisk-volume-tester-84jx5"
May 26 23:25:33.166: INFO: Pod azuredisk-volume-tester-84jx5 has the following logs: 20.0G

STEP: Deleting pod azuredisk-volume-tester-84jx5 in namespace azuredisk-4078
STEP: validating provisioned PV
STEP: checking the PV
... skipping 62 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
May 26 23:26:20.317: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9h478" in namespace "azuredisk-3721" to be "Succeeded or Failed"
May 26 23:26:20.358: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 40.790641ms
May 26 23:26:22.392: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074719018s
May 26 23:26:24.430: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11302346s
May 26 23:26:26.465: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 6.147955132s
May 26 23:26:28.501: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 8.183511098s
May 26 23:26:30.536: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218440469s
... skipping 10 lines ...
May 26 23:26:52.932: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 32.615056029s
May 26 23:26:54.967: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 34.649680949s
May 26 23:26:57.008: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 36.691121341s
May 26 23:26:59.043: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Pending", Reason="", readiness=false. Elapsed: 38.726216982s
May 26 23:27:01.079: INFO: Pod "azuredisk-volume-tester-9h478": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.761812921s
STEP: Saw pod success
May 26 23:27:01.079: INFO: Pod "azuredisk-volume-tester-9h478" satisfied condition "Succeeded or Failed"
May 26 23:27:01.079: INFO: deleting Pod "azuredisk-3721"/"azuredisk-volume-tester-9h478"
May 26 23:27:01.116: INFO: Pod azuredisk-volume-tester-9h478 has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-9h478 in namespace azuredisk-3721
... skipping 69 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
May 26 23:27:58.385: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zs22w" in namespace "azuredisk-2888" to be "Succeeded or Failed"
May 26 23:27:58.423: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 38.009425ms
May 26 23:28:00.457: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072032942s
May 26 23:28:02.491: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106810352s
May 26 23:28:04.526: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.141262278s
May 26 23:28:06.560: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175511332s
May 26 23:28:08.596: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.211871258s
... skipping 10 lines ...
May 26 23:28:30.990: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 32.605479285s
May 26 23:28:33.025: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 34.640836226s
May 26 23:28:35.061: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Pending", Reason="", readiness=false. Elapsed: 36.676351739s
May 26 23:28:37.097: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Running", Reason="", readiness=true. Elapsed: 38.711986512s
May 26 23:28:39.135: INFO: Pod "azuredisk-volume-tester-zs22w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.750672939s
STEP: Saw pod success
May 26 23:28:39.135: INFO: Pod "azuredisk-volume-tester-zs22w" satisfied condition "Succeeded or Failed"
May 26 23:28:39.135: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-zs22w"
May 26 23:28:39.197: INFO: Pod azuredisk-volume-tester-zs22w has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.061165 seconds, 1.6GB/s
hello world

... skipping 52 lines ...
May 26 23:29:26.000: INFO: >>> kubeConfig: /root/tmp261099244/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
May 26 23:29:26.105: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tqjtx" in namespace "azuredisk-8510" to be "Succeeded or Failed"
May 26 23:29:26.138: INFO: Pod "azuredisk-volume-tester-tqjtx": Phase="Pending", Reason="", readiness=false. Elapsed: 33.481103ms
May 26 23:29:28.173: INFO: Pod "azuredisk-volume-tester-tqjtx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068379216s