This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: [WIP]test: workaround capz cluster taint issue
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-11-18 02:44
Elapsed1h6m
Revision5148997e49764e98b9f4902f0b8273f2552f6051
Refs 1600

No Test Failures!


Error lines from build-log.txt

... skipping 767 lines ...
certificate.cert-manager.io "selfsigned-cert" deleted
# Create secret for AzureClusterIdentity
./hack/create-identity-secret.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Error from server (NotFound): secrets "cluster-identity-secret" not found
secret/cluster-identity-secret created
secret/cluster-identity-secret labeled
# Create customized cloud provider configs
./hack/create-custom-cloud-provider-config.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
... skipping 137 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-ew0vxi-kubeconfig; do sleep 1; done"
capz-ew0vxi-kubeconfig                 cluster.x-k8s.io/secret   1      0s
# Get kubeconfig and store it locally.
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-ew0vxi-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done"
error: the server doesn't have a resource type "nodes"
capz-ew0vxi-control-plane-d8j8s   NotReady   <none>   2s    v1.23.15-rc.0.11+2b8076aad0e0b8
run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig ..." to work with the new target cluster
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Waiting for 1 control plane machine(s), 0 worker machine(s), and 2 windows machine(s) to become Ready
node/capz-ew0v-4tmkj condition met
node/capz-ew0v-lzcrd condition met
... skipping 36 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   125k      0 --:--:-- --:--:-- --:--:--  125k
Downloading https://get.helm.sh/helm-v3.10.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 capzci.azurecr.io/azuredisk-csi:v1.25.0-f48f93f1dc60a676e20b7972145d64ae9644a122 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:v1.25.0-f48f93f1dc60a676e20b7972145d64ae9644a122 not found: manifest unknown: manifest tagged by "v1.25.0-f48f93f1dc60a676e20b7972145d64ae9644a122" 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.25.0-f48f93f1dc60a676e20b7972145d64ae9644a122 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=f48f93f1dc60a676e20b7972145d64ae9644a122 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-11-18T03:05:04Z -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 1801 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 617 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.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 219 lines ...
Nov 18 03:16:35.762: INFO: PersistentVolumeClaim pvc-4cwqj found and phase=Bound (4.10997965s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 18 03:16:35.868: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2gxc7" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Nov 18 03:16:35.901: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 33.038564ms
Nov 18 03:16:37.937: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068701102s
Nov 18 03:16:39.972: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10433053s
Nov 18 03:16:42.007: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138622867s
Nov 18 03:16:44.042: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.17432818s
Nov 18 03:16:46.078: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209625308s
... skipping 211 lines ...
Nov 18 03:23:57.868: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Running", Reason="", readiness=true. Elapsed: 7m21.999963049s
Nov 18 03:23:59.904: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Running", Reason="", readiness=true. Elapsed: 7m24.036396315s
Nov 18 03:24:01.941: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Running", Reason="", readiness=true. Elapsed: 7m26.072796528s
Nov 18 03:24:03.978: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Running", Reason="", readiness=false. Elapsed: 7m28.109799088s
Nov 18 03:24:06.013: INFO: Pod "azuredisk-volume-tester-2gxc7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 7m30.145119013s
STEP: Saw pod success
Nov 18 03:24:06.014: INFO: Pod "azuredisk-volume-tester-2gxc7" satisfied condition "Succeeded or Failed"
Nov 18 03:24:06.014: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-2gxc7"
Nov 18 03:24:06.074: INFO: Pod azuredisk-volume-tester-2gxc7 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-2gxc7 in namespace azuredisk-8081
Nov 18 03:24:06.122: INFO: deleting PVC "azuredisk-8081"/"pvc-4cwqj"
Nov 18 03:24:06.122: INFO: Deleting PersistentVolumeClaim "pvc-4cwqj"
... skipping 45 lines ...
Nov 18 03:24:49.371: INFO: PersistentVolumeClaim pvc-xwn96 found but phase is Pending instead of Bound.
Nov 18 03:24:51.405: INFO: PersistentVolumeClaim pvc-xwn96 found and phase=Bound (4.104647702s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Nov 18 03:24:51.508: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7b75f" in namespace "azuredisk-2540" to be "Succeeded or Failed"
Nov 18 03:24:51.542: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 33.530092ms
Nov 18 03:24:53.578: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069201833s
Nov 18 03:24:55.614: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.105227503s
Nov 18 03:24:57.648: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.140100734s
Nov 18 03:24:59.684: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175267285s
Nov 18 03:25:01.718: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209494268s
... skipping 21 lines ...
Nov 18 03:25:46.490: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Running", Reason="", readiness=true. Elapsed: 54.981697158s
Nov 18 03:25:48.526: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Running", Reason="", readiness=true. Elapsed: 57.017169095s
Nov 18 03:25:50.562: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Running", Reason="", readiness=false. Elapsed: 59.053121625s
Nov 18 03:25:52.597: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Running", Reason="", readiness=false. Elapsed: 1m1.088737364s
Nov 18 03:25:54.635: INFO: Pod "azuredisk-volume-tester-7b75f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m3.126152204s
STEP: Saw pod success
Nov 18 03:25:54.635: INFO: Pod "azuredisk-volume-tester-7b75f" satisfied condition "Succeeded or Failed"
Nov 18 03:25:54.635: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-7b75f"
Nov 18 03:25:54.689: INFO: Pod azuredisk-volume-tester-7b75f has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-7b75f in namespace azuredisk-2540
Nov 18 03:25:54.736: INFO: deleting PVC "azuredisk-2540"/"pvc-xwn96"
Nov 18 03:25:54.736: INFO: Deleting PersistentVolumeClaim "pvc-xwn96"
... skipping 45 lines ...
Nov 18 03:26:34.963: INFO: PersistentVolumeClaim pvc-4ws9g found and phase=Bound (4.106138007s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 18 03:26:35.068: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-d2wqx" in namespace "azuredisk-4728" to be "Succeeded or Failed"
Nov 18 03:26:35.100: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 32.840224ms
Nov 18 03:26:37.136: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068606312s
Nov 18 03:26:39.170: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.1020307s
Nov 18 03:26:41.203: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135490024s
Nov 18 03:26:43.240: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171978363s
Nov 18 03:26:45.274: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206591458s
... skipping 19 lines ...
Nov 18 03:27:25.978: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Running", Reason="", readiness=true. Elapsed: 50.910432112s
Nov 18 03:27:28.015: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Running", Reason="", readiness=false. Elapsed: 52.947515878s
Nov 18 03:27:30.051: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Running", Reason="", readiness=false. Elapsed: 54.9833789s
Nov 18 03:27:32.087: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Running", Reason="", readiness=false. Elapsed: 57.019516882s
Nov 18 03:27:34.124: INFO: Pod "azuredisk-volume-tester-d2wqx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 59.056325999s
STEP: Saw pod success
Nov 18 03:27:34.124: INFO: Pod "azuredisk-volume-tester-d2wqx" satisfied condition "Succeeded or Failed"
Nov 18 03:27:34.124: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-d2wqx"
Nov 18 03:27:34.178: INFO: Pod azuredisk-volume-tester-d2wqx has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-d2wqx in namespace azuredisk-4728
Nov 18 03:27:34.222: INFO: deleting PVC "azuredisk-4728"/"pvc-4ws9g"
Nov 18 03:27:34.222: INFO: Deleting PersistentVolumeClaim "pvc-4ws9g"
... skipping 102 lines ...
Nov 18 03:28:20.753: INFO: PersistentVolumeClaim pvc-sfvwz found and phase=Bound (4.101374419s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Nov 18 03:28:20.856: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fv24m" in namespace "azuredisk-5356" to be "Error status code"
Nov 18 03:28:20.892: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 36.214313ms
Nov 18 03:28:22.926: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.070056658s
Nov 18 03:28:24.962: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.106026412s
Nov 18 03:28:26.998: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.14224092s
Nov 18 03:28:29.032: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.176456827s
Nov 18 03:28:31.067: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.210775393s
... skipping 16 lines ...
Nov 18 03:29:05.658: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Pending", Reason="", readiness=false. Elapsed: 44.801769929s
Nov 18 03:29:07.693: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Running", Reason="", readiness=true. Elapsed: 46.837536702s
Nov 18 03:29:09.729: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Running", Reason="", readiness=true. Elapsed: 48.872572393s
Nov 18 03:29:11.766: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Running", Reason="", readiness=true. Elapsed: 50.910243626s
Nov 18 03:29:13.803: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Running", Reason="", readiness=false. Elapsed: 52.946659903s
Nov 18 03:29:15.838: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Running", Reason="", readiness=false. Elapsed: 54.982312001s
Nov 18 03:29:17.875: INFO: Pod "azuredisk-volume-tester-fv24m": Phase="Failed", Reason="", readiness=false. Elapsed: 57.018787066s
STEP: Saw pod failure
Nov 18 03:29:17.875: INFO: Pod "azuredisk-volume-tester-fv24m" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov 18 03:29:17.935: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-fv24m"
Nov 18 03:29:17.977: INFO: Pod azuredisk-volume-tester-fv24m has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied.
At line:1 char:1
+ echo $null >> C:\mnt\test-1\data
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 214 lines ...