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-06-05 03:30
Elapsed51m10s
Revision02635b9dd5b8ab96d781962688d661f3d672bafe
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   186k      0 --:--:-- --:--:-- --:--:--  186k
Downloading https://get.helm.sh/helm-v3.6.0-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-c03845e3f208d4aec69fe50486d7eadb1938aeba || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-c03845e3f208d4aec69fe50486d7eadb1938aeba not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-c03845e3f208d4aec69fe50486d7eadb1938aeba" 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-c03845e3f208d4aec69fe50486d7eadb1938aeba -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=c03845e3f208d4aec69fe50486d7eadb1938aeba -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-05T03:37: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 1304 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-c03845e3f208d4aec69fe50486d7eadb1938aeba || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-c03845e3f208d4aec69fe50486d7eadb1938aeba not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-c03845e3f208d4aec69fe50486d7eadb1938aeba" 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-c03845e3f208d4aec69fe50486d7eadb1938aeba -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=c03845e3f208d4aec69fe50486d7eadb1938aeba -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-05T03:44:56Z -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 1617 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 1006 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 253 lines ...
Go Version: go1.16.4
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0605 03:51:17.959807   14538 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
I0605 03:51:17.962239   14538 azuredisk_v2.go:173] disable UseInstanceMetadata for controller
I0605 03:51:17.963137   14538 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0605 03:51:17.963256   14538 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0605 03:51:17.963288   14538 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0605 03:51:17.963312   14538 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0605 03:51:17.963332   14538 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
Jun  5 03:51:19.401: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gf54q" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jun  5 03:51:19.440: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 38.954167ms
Jun  5 03:51:21.474: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072581623s
Jun  5 03:51:23.509: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108050447s
Jun  5 03:51:25.545: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.143570536s
Jun  5 03:51:27.579: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.177673037s
Jun  5 03:51:29.615: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213488599s
... skipping 8 lines ...
Jun  5 03:51:47.936: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 28.534435256s
Jun  5 03:51:49.973: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 30.571394669s
Jun  5 03:51:52.008: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 32.606366573s
Jun  5 03:51:54.045: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Pending", Reason="", readiness=false. Elapsed: 34.643301881s
Jun  5 03:51:56.079: INFO: Pod "azuredisk-volume-tester-gf54q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.677561431s
STEP: Saw pod success
Jun  5 03:51:56.079: INFO: Pod "azuredisk-volume-tester-gf54q" satisfied condition "Succeeded or Failed"
Jun  5 03:51:56.079: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-gf54q"
Jun  5 03:51:56.173: INFO: Pod azuredisk-volume-tester-gf54q has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-gf54q in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 41 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
Jun  5 03:53:02.003: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-mnl85"
Jun  5 03:53:02.039: INFO: Error getting logs for pod azuredisk-volume-tester-mnl85: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-mnl85)
STEP: Deleting pod azuredisk-volume-tester-mnl85 in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Jun  5 03:53:02.144: INFO: deleting PVC "azuredisk-1318"/"pvc-nzlgw"
Jun  5 03:53:02.144: INFO: Deleting PersistentVolumeClaim "pvc-nzlgw"
STEP: waiting for claim's PV "pvc-a5f9e3c8-7198-4d8c-ae01-ead8671f7aba" 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
Jun  5 03:53:48.815: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-sk8bb" in namespace "azuredisk-694" to be "Succeeded or Failed"
Jun  5 03:53:48.848: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 32.713783ms
Jun  5 03:53:50.883: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067356691s
Jun  5 03:53:52.917: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102022163s
Jun  5 03:53:54.952: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136505073s
Jun  5 03:53:56.986: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170647645s
Jun  5 03:53:59.019: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.203994891s
... skipping 10 lines ...
Jun  5 03:54:21.398: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 32.582533201s
Jun  5 03:54:23.433: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 34.617654721s
Jun  5 03:54:25.468: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 36.652707303s
Jun  5 03:54:27.504: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Pending", Reason="", readiness=false. Elapsed: 38.68871412s
Jun  5 03:54:29.540: INFO: Pod "azuredisk-volume-tester-sk8bb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.724681922s
STEP: Saw pod success
Jun  5 03:54:29.540: INFO: Pod "azuredisk-volume-tester-sk8bb" satisfied condition "Succeeded or Failed"
Jun  5 03:54:29.540: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-sk8bb"
Jun  5 03:54:29.578: INFO: Pod azuredisk-volume-tester-sk8bb has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-sk8bb in namespace azuredisk-694
STEP: validating provisioned PV
STEP: checking the PV
... skipping 39 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
Jun  5 03:55:11.429: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-9kvhl" in namespace "azuredisk-3274" to be "Error status code"
Jun  5 03:55:11.463: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 34.367279ms
Jun  5 03:55:13.498: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068525291s
Jun  5 03:55:15.540: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110455966s
Jun  5 03:55:17.574: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.145106934s
Jun  5 03:55:19.608: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.179135317s
Jun  5 03:55:21.644: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.214527078s
Jun  5 03:55:23.679: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 12.250365051s
Jun  5 03:55:25.714: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 14.285174271s
Jun  5 03:55:27.750: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 16.320858571s
Jun  5 03:55:29.785: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.356366038s
Jun  5 03:55:31.822: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.392450485s
Jun  5 03:55:33.855: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.426027919s
Jun  5 03:55:35.891: INFO: Pod "azuredisk-volume-tester-9kvhl": Phase="Failed", Reason="", readiness=false. Elapsed: 24.461901753s
STEP: Saw pod failure
Jun  5 03:55:35.891: INFO: Pod "azuredisk-volume-tester-9kvhl" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jun  5 03:55:35.928: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-9kvhl"
Jun  5 03:55:35.967: INFO: Pod azuredisk-volume-tester-9kvhl has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-9kvhl 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
Jun  5 04:04:11.253: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tvqhm" in namespace "azuredisk-3090" to be "Succeeded or Failed"
Jun  5 04:04:11.293: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 39.687083ms
Jun  5 04:04:13.327: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073780885s
Jun  5 04:04:15.363: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110292907s
Jun  5 04:04:17.397: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.143878775s
Jun  5 04:04:19.431: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.178057258s
Jun  5 04:04:21.466: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.212891825s
... skipping 2 lines ...
Jun  5 04:04:27.575: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.322221471s
Jun  5 04:04:29.610: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.356682993s
Jun  5 04:04:31.647: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.394423316s
Jun  5 04:04:33.682: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Pending", Reason="", readiness=false. Elapsed: 22.428748132s
Jun  5 04:04:35.716: INFO: Pod "azuredisk-volume-tester-tvqhm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.463312443s
STEP: Saw pod success
Jun  5 04:04:35.727: INFO: Pod "azuredisk-volume-tester-tvqhm" 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
Jun  5 04:04:35.872: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xmmjx" in namespace "azuredisk-3090" to be "Succeeded or Failed"
Jun  5 04:04:35.907: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.643769ms
Jun  5 04:04:37.943: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070695372s
Jun  5 04:04:39.977: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10486407s
Jun  5 04:04:42.014: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.141463588s
Jun  5 04:04:44.049: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.177086665s
Jun  5 04:04:46.085: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213174028s
... skipping 10 lines ...
Jun  5 04:05:08.491: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.618387688s
Jun  5 04:05:10.527: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 34.654747338s
Jun  5 04:05:12.572: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 36.699709836s
Jun  5 04:05:14.607: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Pending", Reason="", readiness=false. Elapsed: 38.734722253s
Jun  5 04:05:16.643: INFO: Pod "azuredisk-volume-tester-xmmjx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.770790333s
STEP: Saw pod success
Jun  5 04:05:16.644: INFO: Pod "azuredisk-volume-tester-xmmjx" satisfied condition "Succeeded or Failed"
Jun  5 04:05:16.644: INFO: deleting Pod "azuredisk-3090"/"azuredisk-volume-tester-xmmjx"
Jun  5 04:05:16.712: INFO: Pod azuredisk-volume-tester-xmmjx has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-xmmjx in namespace azuredisk-3090
STEP: validating provisioned PV
STEP: checking the PV
... skipping 50 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
Jun  5 04:05:54.679: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2bwvl" in namespace "azuredisk-4078" to be "Succeeded or Failed"
Jun  5 04:05:54.717: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 37.811175ms
Jun  5 04:05:56.755: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.076236784s
Jun  5 04:05:58.789: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10956267s
Jun  5 04:06:00.824: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.145290139s
Jun  5 04:06:02.860: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.180777592s
Jun  5 04:06:04.896: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.216791946s
... skipping 10 lines ...
Jun  5 04:06:27.317: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 32.637521063s
Jun  5 04:06:29.352: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 34.673037265s
Jun  5 04:06:31.387: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 36.708018991s
Jun  5 04:06:33.423: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Pending", Reason="", readiness=false. Elapsed: 38.744212029s
Jun  5 04:06:35.458: INFO: Pod "azuredisk-volume-tester-2bwvl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.778446072s
STEP: Saw pod success
Jun  5 04:06:35.458: INFO: Pod "azuredisk-volume-tester-2bwvl" 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
Jun  5 04:06:35.606: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mq9t8" in namespace "azuredisk-4078" to be "Succeeded or Failed"
Jun  5 04:06:35.639: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 33.310537ms
Jun  5 04:06:37.674: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067817044s
Jun  5 04:06:39.708: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102557467s
Jun  5 04:06:41.743: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137443357s
Jun  5 04:06:43.777: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171387755s
Jun  5 04:06:45.812: INFO: Pod "azuredisk-volume-tester-mq9t8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206120544s
... skipping 9 lines ...