This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: chore: refine metrics naming
ResultABORTED
Tests 0 failed / 13 succeeded
Started2022-04-24 07:30
Elapsed39m21s
Revisiondb520906489f26c291de1c1830e4a26b865dc0fc
Refs 1296

No Test Failures!


Show 13 Passed Tests

Show 46 Skipped Tests

Error lines from build-log.txt

... skipping 82 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   205k      0 --:--:-- --:--:-- --:--:--  205k
Downloading https://get.helm.sh/helm-v3.8.2-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azuredisk-csi:v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 not found: manifest unknown: manifest tagged by "v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=9f832dee84b6fa7ac477cdebcee664e29fc604b1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-04-24T07:36:01Z -extldflags "-static""  -mod vendor -o _output/amd64/azurediskplugin.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 1525 lines ...
                    type: string
                type: object
                oneOf:
                - required: ["persistentVolumeClaimName"]
                - required: ["volumeSnapshotContentName"]
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 60 lines ...
                    type: string
                  volumeSnapshotContentName:
                    description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable.
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 254 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 108 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 861 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.4.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - "--leader-election-namespace=kube-system"
            - '-handle-volume-inuse-error=false'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 179 lines ...
Git Commit: N/A
Go Version: go1.18.1
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
W0424 07:45:18.065455   13810 azure_disk_utils.go:165] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
STEP: Building a namespace api object, basename azuredisk
W0424 07:45:18.066119   13810 azuredisk.go:188] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0424 07:45:18.066361   13810 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0424 07:45:18.066391   13810 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0424 07:45:18.066397   13810 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0424 07:45:18.066403   13810 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 71 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:163
STEP: Creating a kubernetes client
Apr 24 07:45:19.050: INFO: >>> kubeConfig: /root/tmp1705275279/kubeconfig/kubeconfig.centralus.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
... skipping 3 lines ...

S [SKIPPING] [0.254 seconds]
Pre-Provisioned
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:37
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:69
    should fail when maxShares is invalid [disk.csi.azure.com][windows] [It]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:163

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
... skipping 54 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
I0424 07:45:20.008811   13810 azuredisk_driver.go:56] Using azure disk driver: kubernetes.io/azure-disk
STEP: Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-h6bycofd/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume"

STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Apr 24 07:45:22.853: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jjx88" in namespace "azuredisk-5194" to be "Succeeded or Failed"
Apr 24 07:45:22.883: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 30.806593ms
Apr 24 07:45:24.912: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059536099s
Apr 24 07:45:26.941: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088623262s
Apr 24 07:45:28.970: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117676618s
Apr 24 07:45:31.000: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 8.147909453s
Apr 24 07:45:33.031: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 10.177984923s
... skipping 2 lines ...
Apr 24 07:45:39.118: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 16.264978328s
Apr 24 07:45:41.147: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 18.294177213s
Apr 24 07:45:43.175: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 20.322692001s
Apr 24 07:45:45.204: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Pending", Reason="", readiness=false. Elapsed: 22.351501506s
Apr 24 07:45:47.233: INFO: Pod "azuredisk-volume-tester-jjx88": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.380517396s
STEP: Saw pod success
Apr 24 07:45:47.233: INFO: Pod "azuredisk-volume-tester-jjx88" satisfied condition "Succeeded or Failed"
Apr 24 07:45:47.233: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-jjx88"
Apr 24 07:45:47.287: INFO: Pod azuredisk-volume-tester-jjx88 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-jjx88 in namespace azuredisk-5194
Apr 24 07:45:47.335: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-5194" for this suite.
... skipping 22 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
Apr 24 07:45:48.023: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5cm5s" in namespace "azuredisk-1353" to be "Succeeded or Failed"
Apr 24 07:45:48.052: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 29.372523ms
Apr 24 07:45:50.081: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057770241s
Apr 24 07:45:52.110: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.087400334s
Apr 24 07:45:54.140: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116531993s
Apr 24 07:45:56.169: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146510699s
Apr 24 07:45:58.200: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.1772742s
Apr 24 07:46:00.230: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 12.206529377s
Apr 24 07:46:02.260: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 14.236877992s
Apr 24 07:46:04.289: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 16.265987313s
Apr 24 07:46:06.319: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Pending", Reason="", readiness=false. Elapsed: 18.296349797s
Apr 24 07:46:08.349: INFO: Pod "azuredisk-volume-tester-5cm5s": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.326246642s
STEP: Saw pod success
Apr 24 07:46:08.349: INFO: Pod "azuredisk-volume-tester-5cm5s" satisfied condition "Succeeded or Failed"
Apr 24 07:46:08.349: INFO: deleting Pod "azuredisk-1353"/"azuredisk-volume-tester-5cm5s"
Apr 24 07:46:08.382: INFO: Pod azuredisk-volume-tester-5cm5s has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-5cm5s in namespace azuredisk-1353
STEP: validating provisioned PV
STEP: checking the PV
... skipping 98 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
Apr 24 07:47:08.708: INFO: deleting Pod "azuredisk-1563"/"azuredisk-volume-tester-pjn6w"
Apr 24 07:47:08.775: INFO: Error getting logs for pod azuredisk-volume-tester-pjn6w: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-pjn6w)
STEP: Deleting pod azuredisk-volume-tester-pjn6w in namespace azuredisk-1563
STEP: validating provisioned PV
STEP: checking the PV
Apr 24 07:47:08.860: INFO: deleting PVC "azuredisk-1563"/"pvc-vstph"
Apr 24 07:47:08.860: INFO: Deleting PersistentVolumeClaim "pvc-vstph"
STEP: waiting for claim's PV "pvc-8f5af2c4-5501-4808-80ab-8d628c46fd90" to be deleted
... skipping 58 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
Apr 24 07:49:35.529: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ts4pd" in namespace "azuredisk-7463" to be "Succeeded or Failed"
Apr 24 07:49:35.557: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 27.748733ms
Apr 24 07:49:37.585: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056416316s
Apr 24 07:49:39.614: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 4.085229125s
Apr 24 07:49:41.644: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 6.114980275s
Apr 24 07:49:43.674: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 8.144653121s
Apr 24 07:49:45.704: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 10.174567234s
Apr 24 07:49:47.733: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 12.203660421s
Apr 24 07:49:49.766: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 14.236462902s
Apr 24 07:49:51.795: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 16.266100319s
Apr 24 07:49:53.825: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Pending", Reason="", readiness=false. Elapsed: 18.295524198s
Apr 24 07:49:55.854: INFO: Pod "azuredisk-volume-tester-ts4pd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.324531748s
STEP: Saw pod success
Apr 24 07:49:55.854: INFO: Pod "azuredisk-volume-tester-ts4pd" satisfied condition "Succeeded or Failed"
Apr 24 07:49:55.854: INFO: deleting Pod "azuredisk-7463"/"azuredisk-volume-tester-ts4pd"
Apr 24 07:49:55.905: INFO: Pod azuredisk-volume-tester-ts4pd has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-ts4pd in namespace azuredisk-7463
STEP: validating provisioned PV
STEP: checking the PV
... 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 an error
Apr 24 07:50:37.064: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-kzllt" in namespace "azuredisk-9241" to be "Error status code"
Apr 24 07:50:37.091: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 27.61429ms
Apr 24 07:50:39.121: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057361422s
Apr 24 07:50:41.151: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.08700045s
Apr 24 07:50:43.180: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116912438s
Apr 24 07:50:45.210: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146197131s
Apr 24 07:50:47.240: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.176073454s
Apr 24 07:50:49.269: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 12.205134541s
Apr 24 07:50:51.298: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 14.234588752s
Apr 24 07:50:53.328: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 16.264163574s
Apr 24 07:50:55.357: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Pending", Reason="", readiness=false. Elapsed: 18.293065592s
Apr 24 07:50:57.386: INFO: Pod "azuredisk-volume-tester-kzllt": Phase="Failed", Reason="", readiness=false. Elapsed: 20.322546708s
STEP: Saw pod failure
Apr 24 07:50:57.386: INFO: Pod "azuredisk-volume-tester-kzllt" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr 24 07:50:57.421: INFO: deleting Pod "azuredisk-9241"/"azuredisk-volume-tester-kzllt"
Apr 24 07:50:57.452: INFO: Pod azuredisk-volume-tester-kzllt has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-kzllt in namespace azuredisk-9241
STEP: validating provisioned PV
... skipping 382 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
Apr 24 07:59:08.507: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-8b45d" in namespace "azuredisk-1387" to be "Succeeded or Failed"
Apr 24 07:59:08.533: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 25.547005ms
Apr 24 07:59:10.558: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.051270449s
Apr 24 07:59:12.585: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.077514298s
Apr 24 07:59:14.611: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1044359s
Apr 24 07:59:16.638: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.131168828s
Apr 24 07:59:18.666: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.158635177s
... skipping 4 lines ...
Apr 24 07:59:28.798: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 20.290816742s
Apr 24 07:59:30.825: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 22.318026547s
Apr 24 07:59:32.853: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 24.346060762s
Apr 24 07:59:34.880: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Pending", Reason="", readiness=false. Elapsed: 26.37286979s
Apr 24 07:59:36.907: INFO: Pod "azuredisk-volume-tester-8b45d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.399501864s
STEP: Saw pod success
Apr 24 07:59:36.907: INFO: Pod "azuredisk-volume-tester-8b45d" satisfied condition "Succeeded or Failed"
Apr 24 07:59:36.907: INFO: deleting Pod "azuredisk-1387"/"azuredisk-volume-tester-8b45d"
Apr 24 07:59:36.961: INFO: Pod azuredisk-volume-tester-8b45d has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-8b45d in namespace azuredisk-1387
... skipping 77 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
Apr 24 08:01:08.817: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qkbq4" in namespace "azuredisk-4547" to be "Succeeded or Failed"
Apr 24 08:01:08.848: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 31.175691ms
Apr 24 08:01:10.877: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.060177575s
Apr 24 08:01:12.907: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.090038844s
Apr 24 08:01:14.937: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120410492s
Apr 24 08:01:16.967: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.150098324s
Apr 24 08:01:18.996: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.179267943s
... skipping 4 lines ...
Apr 24 08:01:29.145: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.327468884s
Apr 24 08:01:31.174: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.356870296s
Apr 24 08:01:33.203: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 24.386151289s
Apr 24 08:01:35.232: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Pending", Reason="", readiness=false. Elapsed: 26.415175823s
Apr 24 08:01:37.261: INFO: Pod "azuredisk-volume-tester-qkbq4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.444202358s
STEP: Saw pod success
Apr 24 08:01:37.261: INFO: Pod "azuredisk-volume-tester-qkbq4" satisfied condition "Succeeded or Failed"
Apr 24 08:01:37.261: INFO: deleting Pod "azuredisk-4547"/"azuredisk-volume-tester-qkbq4"
Apr 24 08:01:37.316: INFO: Pod azuredisk-volume-tester-qkbq4 has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.053897 seconds, 1.8GB/s
hello world

... skipping 118 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
Apr 24 08:02:29.912: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-8f5pt" in namespace "azuredisk-7578" to be "Succeeded or Failed"
Apr 24 08:02:29.940: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 28.421004ms
Apr 24 08:02:31.971: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059115939s
Apr 24 08:02:34.001: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088662089s
Apr 24 08:02:36.030: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118099816s
Apr 24 08:02:38.060: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 8.148442185s
Apr 24 08:02:40.089: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 10.177140579s
... skipping 10 lines ...
Apr 24 08:03:02.418: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 32.506221773s
Apr 24 08:03:04.447: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 34.535339903s
Apr 24 08:03:06.477: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 36.565037323s
Apr 24 08:03:08.506: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Pending", Reason="", readiness=false. Elapsed: 38.594375562s
Apr 24 08:03:10.535: INFO: Pod "azuredisk-volume-tester-8f5pt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.623303145s
STEP: Saw pod success
Apr 24 08:03:10.535: INFO: Pod "azuredisk-volume-tester-8f5pt" satisfied condition "Succeeded or Failed"
Apr 24 08:03:10.535: INFO: deleting Pod "azuredisk-7578"/"azuredisk-volume-tester-8f5pt"
Apr 24 08:03:10.596: INFO: Pod azuredisk-volume-tester-8f5pt has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-8f5pt in namespace azuredisk-7578
STEP: validating provisioned PV
STEP: checking the PV
... skipping 251 lines ...