This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: [WIP]chore: remove VOLUME_MOUNT_GROUP cap
ResultABORTED
Tests 0 failed / 31 succeeded
Started2022-05-12 06:43
Elapsed48m9s
Revision3947bb1d11a9bc1fc820b35f1821acc93cf20734
Refs 1018

No Test Failures!


Show 31 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 668 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
# Deploy CAPI
curl --retry 3 -sSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.2/cluster-api-components.yaml | /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/envsubst-v2.0.0-20210730161058-179042472c46 | kubectl apply -f -
namespace/capi-system created
customresourcedefinition.apiextensions.k8s.io/clusterclasses.cluster.x-k8s.io created
... skipping 132 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-5e0sgg-kubeconfig; do sleep 1; done"
capz-5e0sgg-kubeconfig                 cluster.x-k8s.io/secret               1      0s
# Get kubeconfig and store it locally.
kubectl get secrets capz-5e0sgg-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! kubectl --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done"
error: the server doesn't have a resource type "nodes"
capz-5e0sgg-control-plane-pbldd   NotReady   control-plane,master   5s    v1.22.1
run "kubectl --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), 2 worker machine(s), and  windows machine(s) to become Ready
node/capz-5e0sgg-control-plane-pbldd condition met
node/capz-5e0sgg-md-0-8749b condition met
... skipping 35 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   198k      0 --:--:-- --:--:-- --:--:--  198k
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 capzci.azurecr.io/azurefile-csi:e2e-c52c48007cdd2c836422f7b2374338f4e15ae788 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-c52c48007cdd2c836422f7b2374338f4e15ae788 not found: manifest unknown: manifest tagged by "e2e-c52c48007cdd2c836422f7b2374338f4e15ae788" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.driverVersion=e2e-c52c48007cdd2c836422f7b2374338f4e15ae788 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=c52c48007cdd2c836422f7b2374338f4e15ae788 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-05-12T06:57:12Z -s -w -extldflags '-static'" -mod vendor -o _output/amd64/azurefileplugin.exe ./pkg/azurefileplugin
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 1797 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 938 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'
            - '-timeout=120s'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          imagePullPolicy: IfNotPresent
... skipping 209 lines ...
Git Commit: N/A
Go Version: go1.18.1
Platform: linux/amd64

Streaming logs below:
STEP: Building a namespace api object, basename azurefile
W0512 07:09:43.344036   36820 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
I0512 07:09:43.350497   36820 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME
I0512 07:09:43.350560   36820 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0512 07:09:43.350576   36820 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0512 07:09:43.350598   36820 driver.go:93] Enabling controller service capability: EXPAND_VOLUME
I0512 07:09:43.350612   36820 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER
I0512 07:09:43.350637   36820 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER
... skipping 23 lines ...
May 12 07:10:10.706: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-7752w] to have phase Bound
May 12 07:10:10.808: INFO: PersistentVolumeClaim pvc-7752w found and phase=Bound (102.587764ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with an error
May 12 07:10:11.123: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-qbxmj" in namespace "azurefile-8081" to be "Error status code"
May 12 07:10:11.226: INFO: Pod "azurefile-volume-tester-qbxmj": Phase="Pending", Reason="", readiness=false. Elapsed: 102.637165ms
May 12 07:10:13.342: INFO: Pod "azurefile-volume-tester-qbxmj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218989748s
May 12 07:10:15.456: INFO: Pod "azurefile-volume-tester-qbxmj": Phase="Failed", Reason="", readiness=false. Elapsed: 4.33253939s
STEP: Saw pod failure
May 12 07:10:15.456: INFO: Pod "azurefile-volume-tester-qbxmj" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May 12 07:10:15.576: INFO: deleting Pod "azurefile-8081"/"azurefile-volume-tester-qbxmj"
May 12 07:10:15.688: INFO: Pod azurefile-volume-tester-qbxmj has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-qbxmj in namespace azurefile-8081
May 12 07:10:15.807: INFO: deleting PVC "azurefile-8081"/"pvc-7752w"
... skipping 37 lines ...
May 12 07:10:20.191: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lgw5g] to have phase Bound
May 12 07:10:20.295: INFO: PersistentVolumeClaim pvc-lgw5g found and phase=Bound (103.086447ms)
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
May 12 07:10:20.605: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-cvmt2" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:20.707: INFO: Pod "azurefile-volume-tester-cvmt2": Phase="Pending", Reason="", readiness=false. Elapsed: 102.521164ms
May 12 07:10:22.817: INFO: Pod "azurefile-volume-tester-cvmt2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.212554119s
STEP: Saw pod success
May 12 07:10:22.817: INFO: Pod "azurefile-volume-tester-cvmt2" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
May 12 07:10:23.027: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5j5h6] to have phase Bound
May 12 07:10:23.130: INFO: PersistentVolumeClaim pvc-5j5h6 found and phase=Bound (103.454637ms)
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
May 12 07:10:23.441: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-r8qkd" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:23.543: INFO: Pod "azurefile-volume-tester-r8qkd": Phase="Pending", Reason="", readiness=false. Elapsed: 102.447507ms
May 12 07:10:25.654: INFO: Pod "azurefile-volume-tester-r8qkd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.213593493s
STEP: Saw pod success
May 12 07:10:25.654: INFO: Pod "azurefile-volume-tester-r8qkd" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
May 12 07:10:25.862: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-z96bz] to have phase Bound
May 12 07:10:25.964: INFO: PersistentVolumeClaim pvc-z96bz found and phase=Bound (102.359421ms)
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
May 12 07:10:26.275: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-6tfzr" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:26.378: INFO: Pod "azurefile-volume-tester-6tfzr": Phase="Pending", Reason="", readiness=false. Elapsed: 103.055129ms
May 12 07:10:28.489: INFO: Pod "azurefile-volume-tester-6tfzr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.213234216s
STEP: Saw pod success
May 12 07:10:28.489: INFO: Pod "azurefile-volume-tester-6tfzr" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
May 12 07:10:28.697: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-v8qpx] to have phase Bound
May 12 07:10:28.799: INFO: PersistentVolumeClaim pvc-v8qpx found and phase=Bound (102.216652ms)
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
May 12 07:10:29.112: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-dwlxx" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:29.214: INFO: Pod "azurefile-volume-tester-dwlxx": Phase="Pending", Reason="", readiness=false. Elapsed: 102.74475ms
May 12 07:10:31.324: INFO: Pod "azurefile-volume-tester-dwlxx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.211928018s
STEP: Saw pod success
May 12 07:10:31.324: INFO: Pod "azurefile-volume-tester-dwlxx" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
May 12 07:10:31.531: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8q7tb] to have phase Bound
May 12 07:10:31.634: INFO: PersistentVolumeClaim pvc-8q7tb found and phase=Bound (103.032945ms)
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
May 12 07:10:31.944: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-dzt8j" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:32.048: INFO: Pod "azurefile-volume-tester-dzt8j": Phase="Pending", Reason="", readiness=false. Elapsed: 103.063891ms
May 12 07:10:34.157: INFO: Pod "azurefile-volume-tester-dzt8j": Phase="Running", Reason="", readiness=true. Elapsed: 2.212765869s
May 12 07:10:36.267: INFO: Pod "azurefile-volume-tester-dzt8j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.322798318s
STEP: Saw pod success
May 12 07:10:36.267: INFO: Pod "azurefile-volume-tester-dzt8j" satisfied condition "Succeeded or Failed"
STEP: setting up the PV
STEP: creating a PV
STEP: setting up the PVC
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
May 12 07:10:36.476: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-xhq2j] to have phase Bound
May 12 07:10:36.579: INFO: PersistentVolumeClaim pvc-xhq2j found and phase=Bound (102.774142ms)
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
May 12 07:10:36.890: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-5nzrq" in namespace "azurefile-2540" to be "Succeeded or Failed"
May 12 07:10:36.993: INFO: Pod "azurefile-volume-tester-5nzrq": Phase="Pending", Reason="", readiness=false. Elapsed: 102.273556ms
May 12 07:10:39.102: INFO: Pod "azurefile-volume-tester-5nzrq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.211360043s
STEP: Saw pod success
May 12 07:10:39.102: INFO: Pod "azurefile-volume-tester-5nzrq" satisfied condition "Succeeded or Failed"
May 12 07:10:39.102: INFO: deleting Pod "azurefile-2540"/"azurefile-volume-tester-5nzrq"
May 12 07:10:39.206: INFO: Pod azurefile-volume-tester-5nzrq has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-5nzrq in namespace azurefile-2540
May 12 07:10:39.323: INFO: deleting PVC "azurefile-2540"/"pvc-xhq2j"
May 12 07:10:39.323: INFO: Deleting PersistentVolumeClaim "pvc-xhq2j"
... skipping 143 lines ...
May 12 07:10:50.524: INFO: PersistentVolumeClaim pvc-tkdcj found but phase is Pending instead of Bound.
May 12 07:10:52.627: INFO: PersistentVolumeClaim pvc-tkdcj found and phase=Bound (2.205997794s)
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
May 12 07:10:52.937: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-xxnhm" in namespace "azurefile-5466" to be "Succeeded or Failed"
May 12 07:10:53.039: INFO: Pod "azurefile-volume-tester-xxnhm": Phase="Pending", Reason="", readiness=false. Elapsed: 102.209245ms
May 12 07:10:55.149: INFO: Pod "azurefile-volume-tester-xxnhm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.212075956s
STEP: Saw pod success
May 12 07:10:55.149: INFO: Pod "azurefile-volume-tester-xxnhm" satisfied condition "Succeeded or Failed"
May 12 07:10:55.149: INFO: deleting Pod "azurefile-5466"/"azurefile-volume-tester-xxnhm"
May 12 07:10:55.254: INFO: Pod azurefile-volume-tester-xxnhm has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-xxnhm in namespace azurefile-5466
May 12 07:10:55.374: INFO: deleting PVC "azurefile-5466"/"pvc-tkdcj"
May 12 07:10:55.374: INFO: Deleting PersistentVolumeClaim "pvc-tkdcj"
... skipping 33 lines ...
May 12 07:10:59.025: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5vf7t] to have phase Bound
May 12 07:10:59.128: INFO: PersistentVolumeClaim pvc-5vf7t found and phase=Bound (102.490695ms)
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
May 12 07:10:59.439: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-wcc6n" in namespace "azurefile-2790" to be "Succeeded or Failed"
May 12 07:10:59.542: INFO: Pod "azurefile-volume-tester-wcc6n": Phase="Pending", Reason="", readiness=false. Elapsed: 102.468336ms
May 12 07:11:01.652: INFO: Pod "azurefile-volume-tester-wcc6n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.212021436s
STEP: Saw pod success
May 12 07:11:01.652: INFO: Pod "azurefile-volume-tester-wcc6n" satisfied condition "Succeeded or Failed"
May 12 07:11:01.652: INFO: deleting Pod "azurefile-2790"/"azurefile-volume-tester-wcc6n"
May 12 07:11:01.756: INFO: Pod azurefile-volume-tester-wcc6n has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-wcc6n in namespace azurefile-2790
May 12 07:11:01.876: INFO: deleting PVC "azurefile-2790"/"pvc-5vf7t"
May 12 07:11:01.876: INFO: Deleting PersistentVolumeClaim "pvc-5vf7t"
... skipping 132 lines ...
May 12 07:13:05.717: INFO: PersistentVolumeClaim pvc-28qvh found but phase is Pending instead of Bound.
May 12 07:13:07.822: INFO: PersistentVolumeClaim pvc-28qvh found and phase=Bound (1m39.000787769s)
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
May 12 07:13:08.133: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-7wcnx" in namespace "azurefile-5194" to be "Succeeded or Failed"
May 12 07:13:08.236: INFO: Pod "azurefile-volume-tester-7wcnx": Phase="Pending", Reason="", readiness=false. Elapsed: 103.090707ms
May 12 07:13:10.345: INFO: Pod "azurefile-volume-tester-7wcnx": Phase="Running", Reason="", readiness=true. Elapsed: 2.211837401s
May 12 07:13:12.454: INFO: Pod "azurefile-volume-tester-7wcnx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.320709588s
STEP: Saw pod success
May 12 07:13:12.454: INFO: Pod "azurefile-volume-tester-7wcnx" satisfied condition "Succeeded or Failed"
May 12 07:13:12.454: INFO: deleting Pod "azurefile-5194"/"azurefile-volume-tester-7wcnx"
May 12 07:13:12.565: INFO: Pod azurefile-volume-tester-7wcnx has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-7wcnx in namespace azurefile-5194
May 12 07:13:12.681: INFO: deleting PVC "azurefile-5194"/"pvc-28qvh"
May 12 07:13:12.681: INFO: Deleting PersistentVolumeClaim "pvc-28qvh"
... skipping 35 lines ...
May 12 07:13:20.412: INFO: PersistentVolumeClaim pvc-pbfdk found but phase is Pending instead of Bound.
May 12 07:13:22.516: INFO: PersistentVolumeClaim pvc-pbfdk found and phase=Bound (2.206715636s)
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
May 12 07:13:22.828: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-kpbmx" in namespace "azurefile-1353" to be "Succeeded or Failed"
May 12 07:13:22.931: INFO: Pod "azurefile-volume-tester-kpbmx": Phase="Pending", Reason="", readiness=false. Elapsed: 102.32284ms
May 12 07:13:25.040: INFO: Pod "azurefile-volume-tester-kpbmx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.211430768s
STEP: Saw pod success
May 12 07:13:25.040: INFO: Pod "azurefile-volume-tester-kpbmx" satisfied condition "Succeeded or Failed"
May 12 07:13:25.040: INFO: deleting Pod "azurefile-1353"/"azurefile-volume-tester-kpbmx"
May 12 07:13:25.145: INFO: Pod azurefile-volume-tester-kpbmx has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-kpbmx in namespace azurefile-1353
May 12 07:13:25.261: INFO: deleting PVC "azurefile-1353"/"pvc-pbfdk"
May 12 07:13:25.261: INFO: Deleting PersistentVolumeClaim "pvc-pbfdk"
... skipping 128 lines ...
May 12 07:15:20.647: INFO: PersistentVolumeClaim pvc-f5d4p found but phase is Pending instead of Bound.
May 12 07:15:22.751: INFO: PersistentVolumeClaim pvc-f5d4p found and phase=Bound (21.136637808s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with an error
May 12 07:15:23.067: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-rxkv9" in namespace "azurefile-156" to be "Error status code"
May 12 07:15:23.170: INFO: Pod "azurefile-volume-tester-rxkv9": Phase="Pending", Reason="", readiness=false. Elapsed: 102.965589ms
May 12 07:15:25.278: INFO: Pod "azurefile-volume-tester-rxkv9": Phase="Failed", Reason="", readiness=false. Elapsed: 2.21126598s
STEP: Saw pod failure
May 12 07:15:25.278: INFO: Pod "azurefile-volume-tester-rxkv9" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May 12 07:15:25.386: INFO: deleting Pod "azurefile-156"/"azurefile-volume-tester-rxkv9"
May 12 07:15:25.491: INFO: Pod azurefile-volume-tester-rxkv9 has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-rxkv9 in namespace azurefile-156
May 12 07:15:25.612: INFO: deleting PVC "azurefile-156"/"pvc-f5d4p"
... skipping 195 lines ...
May 12 07:17:18.692: INFO: PersistentVolumeClaim pvc-g5r9z found but phase is Pending instead of Bound.
May 12 07:17:20.796: INFO: PersistentVolumeClaim pvc-g5r9z found and phase=Bound (2.206269056s)
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
May 12 07:17:21.106: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-q7hdr" in namespace "azurefile-2546" to be "Succeeded or Failed"
May 12 07:17:21.208: INFO: Pod "azurefile-volume-tester-q7hdr": Phase="Pending", Reason="", readiness=false. Elapsed: 101.985304ms
May 12 07:17:23.317: INFO: Pod "azurefile-volume-tester-q7hdr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.211224735s
STEP: Saw pod success
May 12 07:17:23.317: INFO: Pod "azurefile-volume-tester-q7hdr" satisfied condition "Succeeded or Failed"
STEP: resizing the pvc
STEP: sleep 30s waiting for resize complete
STEP: checking the resizing result
STEP: checking the resizing PV result
STEP: checking the resizing azurefile result
May 12 07:17:54.432: INFO: deleting Pod "azurefile-2546"/"azurefile-volume-tester-q7hdr"
... skipping 39 lines ...
May 12 07:17:57.294: INFO: PersistentVolumeClaim pvc-rk2gj found but phase is Pending instead of Bound.
May 12 07:17:59.398: INFO: PersistentVolumeClaim pvc-rk2gj found and phase=Bound (2.207089434s)
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
May 12 07:17:59.708: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-rfrxw" in namespace "azurefile-1598" to be "Succeeded or Failed"
May 12 07:17:59.810: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Pending", Reason="", readiness=false. Elapsed: 102.195649ms
May 12 07:18:01.914: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.206236318s
May 12 07:18:04.019: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.310823197s
May 12 07:18:06.123: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.415087698s
May 12 07:18:08.233: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.524943086s
May 12 07:18:10.342: INFO: Pod "azurefile-volume-tester-rfrxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.634081374s
STEP: Saw pod success
May 12 07:18:10.342: INFO: Pod "azurefile-volume-tester-rfrxw" satisfied condition "Succeeded or Failed"
May 12 07:18:10.342: INFO: deleting Pod "azurefile-1598"/"azurefile-volume-tester-rfrxw"
May 12 07:18:10.447: INFO: Pod azurefile-volume-tester-rfrxw has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-rfrxw in namespace azurefile-1598
May 12 07:18:10.562: INFO: deleting PVC "azurefile-1598"/"pvc-rk2gj"
May 12 07:18:10.562: INFO: Deleting PersistentVolumeClaim "pvc-rk2gj"
... skipping 36 lines ...
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
May 12 07:18:17.805: INFO: deleting Pod "azurefile-3410"/"azurefile-volume-tester-czlsc"
May 12 07:18:17.909: INFO: Error getting logs for pod azurefile-volume-tester-czlsc: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-czlsc)
STEP: Deleting pod azurefile-volume-tester-czlsc in namespace azurefile-3410
May 12 07:18:18.014: INFO: deleting PVC "azurefile-3410"/"pvc-wz9xs"
May 12 07:18:18.014: INFO: Deleting PersistentVolumeClaim "pvc-wz9xs"
STEP: waiting for claim's PV "pvc-7b023518-15b2-4850-9166-2b83e9b4ee9f" to be deleted
May 12 07:18:18.326: INFO: Waiting up to 10m0s for PersistentVolume pvc-7b023518-15b2-4850-9166-2b83e9b4ee9f to get deleted
May 12 07:18:18.429: INFO: PersistentVolume pvc-7b023518-15b2-4850-9166-2b83e9b4ee9f found and phase=Bound (102.722725ms)
... skipping 57 lines ...
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
May 12 07:20:28.225: INFO: deleting Pod "azurefile-8582"/"azurefile-volume-tester-sb4wd"
May 12 07:20:28.340: INFO: Error getting logs for pod azurefile-volume-tester-sb4wd: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-sb4wd)
STEP: Deleting pod azurefile-volume-tester-sb4wd in namespace azurefile-8582
May 12 07:20:28.443: INFO: deleting PVC "azurefile-8582"/"pvc-fjpfk"
May 12 07:20:28.443: INFO: Deleting PersistentVolumeClaim "pvc-fjpfk"
STEP: waiting for claim's PV "pvc-08b36c3b-1b39-4faa-a235-70d01cabf556" to be deleted
May 12 07:20:28.751: INFO: Waiting up to 10m0s for PersistentVolume pvc-08b36c3b-1b39-4faa-a235-70d01cabf556 to get deleted
May 12 07:20:28.853: INFO: PersistentVolume pvc-08b36c3b-1b39-4faa-a235-70d01cabf556 found and phase=Bound (101.648445ms)
... skipping 87 lines ...