This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: add allowEmptyCloudConfig config in chart
ResultABORTED
Tests 0 failed / 31 succeeded
Started2021-11-09 11:04
Elapsed50m4s
Revision3540e6d33a7836eb972a295500faf9503d597b70
Refs 840

No Test Failures!


Show 31 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 72 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11148  100 11148    0     0   149k      0 --:--:-- --:--:-- --:--:--  151k
Downloading https://get.helm.sh/helm-v3.7.1-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/azurefile-csi:e2e-8cee5f367f67080360c762181c5d2b5b342a4280 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-8cee5f367f67080360c762181c5d2b5b342a4280 not found: manifest unknown: manifest tagged by "e2e-8cee5f367f67080360c762181c5d2b5b342a4280" 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-8cee5f367f67080360c762181c5d2b5b342a4280 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=8cee5f367f67080360c762181c5d2b5b342a4280 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2021-11-09T11:10:09Z -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 2078 lines ...
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'volumeSnapshotClassName is the name of the VolumeSnapshotClass
                  requested by the VolumeSnapshot. If not specified, the default snapshot
                  class will be used if one exists. If not specified, and there is
                  no default snapshot class, dynamic snapshot creation will fail.
                  Empty string is not allowed for this field. TODO(xiangqian): a webhook
                  validation on empty string. More info: https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes'
                type: string
            required:
            - source
            type: object
... skipping 22 lines ...
                  pre-existing snapshot, this field will be filled with the "creation_time"
                  value returned from the CSI "ListSnapshots" gRPC call if the driver
                  supports it. If not specified, it indicates that the creation time
                  of the snapshot is unknown.
                format: date-time
                type: string
              error:
                description: error is the last observed error during snapshot creation,
                  if any. This field could be helpful to upper level controllers(i.e.,
                  application controller) to decide whether they should continue on
                  waiting for the snapshot to be created based on the type of error
                  reported.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 10 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                x-kubernetes-int-or-string: true
            type: object
        required:
        - spec
... skipping 265 lines ...
                  supports it. If not specified, it indicates the creation time is
                  unknown. The format of this field is a Unix nanoseconds time encoded
                  as an int64. On Unix, the command `date +%s%N` returns the current
                  time in nanoseconds since 1970-01-01 00:00:00 UTC.
                format: int64
                type: integer
              error:
                description: error is the latest observed error during snapshot creation,
                  if any.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 9 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                format: int64
                minimum: 0
                type: integer
              snapshotHandle:
                description: snapshotHandle is the CSI "snapshot_id" of a snapshot
                  on the underlying storage system. If not specified, it indicates
                  that dynamic snapshot creation has either failed or it is still
                  in progress.
                type: string
            type: object
        required:
        - spec
        type: object
... skipping 936 lines ...
        - name: csi-resizer
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.3.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - '-handle-volume-inuse-error=false'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: socket-dir
... skipping 202 lines ...
Driver Version: N/A
Git Commit: N/A
Go Version: go1.17.3
Platform: linux/amd64

Streaming logs below:
W1109 11:33:54.277962   12544 azure.go:77] 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 azurefile
I1109 11:33:54.279446   12544 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME
I1109 11:33:54.279475   12544 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I1109 11:33:54.279479   12544 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I1109 11:33:54.279483   12544 driver.go:93] Enabling controller service capability: EXPAND_VOLUME
I1109 11:33:54.279486   12544 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER
... skipping 23 lines ...
Nov  9 11:34:23.263: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-94mhq] to have phase Bound
Nov  9 11:34:23.374: INFO: PersistentVolumeClaim pvc-94mhq found and phase=Bound (110.249801ms)
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
Nov  9 11:34:23.704: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-pr5st" in namespace "azurefile-8081" to be "Error status code"
Nov  9 11:34:23.813: INFO: Pod "azurefile-volume-tester-pr5st": Phase="Pending", Reason="", readiness=false. Elapsed: 109.114085ms
Nov  9 11:34:25.924: INFO: Pod "azurefile-volume-tester-pr5st": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21946779s
Nov  9 11:34:28.035: INFO: Pod "azurefile-volume-tester-pr5st": Phase="Failed", Reason="", readiness=false. Elapsed: 4.330450513s
STEP: Saw pod failure
Nov  9 11:34:28.035: INFO: Pod "azurefile-volume-tester-pr5st" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov  9 11:34:28.178: INFO: deleting Pod "azurefile-8081"/"azurefile-volume-tester-pr5st"
Nov  9 11:34:28.292: INFO: Pod azurefile-volume-tester-pr5st has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-pr5st in namespace azurefile-8081
Nov  9 11:34:28.410: INFO: deleting PVC "azurefile-8081"/"pvc-94mhq"
... skipping 37 lines ...
Nov  9 11:34:33.951: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8mhhp] to have phase Bound
Nov  9 11:34:34.060: INFO: PersistentVolumeClaim pvc-8mhhp found and phase=Bound (109.399275ms)
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  9 11:34:34.390: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-dtgl4" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:34.499: INFO: Pod "azurefile-volume-tester-dtgl4": Phase="Pending", Reason="", readiness=false. Elapsed: 109.086191ms
Nov  9 11:34:36.610: INFO: Pod "azurefile-volume-tester-dtgl4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.219973012s
STEP: Saw pod success
Nov  9 11:34:36.610: INFO: Pod "azurefile-volume-tester-dtgl4" 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"
Nov  9 11:34:36.832: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-6v45l] to have phase Bound
Nov  9 11:34:36.942: INFO: PersistentVolumeClaim pvc-6v45l found and phase=Bound (110.303557ms)
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  9 11:34:37.273: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-fcsw2" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:37.382: INFO: Pod "azurefile-volume-tester-fcsw2": Phase="Pending", Reason="", readiness=false. Elapsed: 109.731182ms
Nov  9 11:34:39.495: INFO: Pod "azurefile-volume-tester-fcsw2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.222738896s
STEP: Saw pod success
Nov  9 11:34:39.496: INFO: Pod "azurefile-volume-tester-fcsw2" 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"
Nov  9 11:34:39.716: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-dmwxr] to have phase Bound
Nov  9 11:34:39.827: INFO: PersistentVolumeClaim pvc-dmwxr found and phase=Bound (110.224325ms)
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  9 11:34:40.156: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-j9r2d" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:40.266: INFO: Pod "azurefile-volume-tester-j9r2d": Phase="Pending", Reason="", readiness=false. Elapsed: 109.888383ms
Nov  9 11:34:42.378: INFO: Pod "azurefile-volume-tester-j9r2d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.22189692s
STEP: Saw pod success
Nov  9 11:34:42.378: INFO: Pod "azurefile-volume-tester-j9r2d" 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"
Nov  9 11:34:42.600: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-rrw84] to have phase Bound
Nov  9 11:34:42.710: INFO: PersistentVolumeClaim pvc-rrw84 found and phase=Bound (109.633257ms)
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  9 11:34:43.042: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-xs4c6" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:43.152: INFO: Pod "azurefile-volume-tester-xs4c6": Phase="Pending", Reason="", readiness=false. Elapsed: 109.589611ms
Nov  9 11:34:45.264: INFO: Pod "azurefile-volume-tester-xs4c6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.22126787s
Nov  9 11:34:47.375: INFO: Pod "azurefile-volume-tester-xs4c6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.33281258s
STEP: Saw pod success
Nov  9 11:34:47.375: INFO: Pod "azurefile-volume-tester-xs4c6" 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"
Nov  9 11:34:47.602: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-mpm2h] to have phase Bound
Nov  9 11:34:47.712: INFO: PersistentVolumeClaim pvc-mpm2h found and phase=Bound (110.004108ms)
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  9 11:34:48.046: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-4ss8k" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:48.156: INFO: Pod "azurefile-volume-tester-4ss8k": Phase="Pending", Reason="", readiness=false. Elapsed: 109.768375ms
Nov  9 11:34:50.271: INFO: Pod "azurefile-volume-tester-4ss8k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.224697303s
Nov  9 11:34:52.384: INFO: Pod "azurefile-volume-tester-4ss8k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.337196162s
STEP: Saw pod success
Nov  9 11:34:52.384: INFO: Pod "azurefile-volume-tester-4ss8k" 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"
Nov  9 11:34:52.607: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-d6p8t] to have phase Bound
Nov  9 11:34:52.718: INFO: PersistentVolumeClaim pvc-d6p8t found and phase=Bound (111.15668ms)
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  9 11:34:53.052: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-s7hwm" in namespace "azurefile-1318" to be "Succeeded or Failed"
Nov  9 11:34:53.163: INFO: Pod "azurefile-volume-tester-s7hwm": Phase="Pending", Reason="", readiness=false. Elapsed: 110.113145ms
Nov  9 11:34:55.275: INFO: Pod "azurefile-volume-tester-s7hwm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.222323469s
STEP: Saw pod success
Nov  9 11:34:55.275: INFO: Pod "azurefile-volume-tester-s7hwm" satisfied condition "Succeeded or Failed"
Nov  9 11:34:55.275: INFO: deleting Pod "azurefile-1318"/"azurefile-volume-tester-s7hwm"
Nov  9 11:34:55.389: INFO: Pod azurefile-volume-tester-s7hwm has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-s7hwm in namespace azurefile-1318
Nov  9 11:34:55.507: INFO: deleting PVC "azurefile-1318"/"pvc-d6p8t"
Nov  9 11:34:55.508: INFO: Deleting PersistentVolumeClaim "pvc-d6p8t"
... skipping 148 lines ...
Nov  9 11:35:10.297: INFO: PersistentVolumeClaim pvc-gx49p found but phase is Pending instead of Bound.
Nov  9 11:35:12.409: INFO: PersistentVolumeClaim pvc-gx49p found and phase=Bound (2.221344238s)
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  9 11:35:12.739: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-28sgr" in namespace "azurefile-3274" to be "Succeeded or Failed"
Nov  9 11:35:12.849: INFO: Pod "azurefile-volume-tester-28sgr": Phase="Pending", Reason="", readiness=false. Elapsed: 109.534553ms
Nov  9 11:35:14.960: INFO: Pod "azurefile-volume-tester-28sgr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220384104s
Nov  9 11:35:17.071: INFO: Pod "azurefile-volume-tester-28sgr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.331300292s
STEP: Saw pod success
Nov  9 11:35:17.071: INFO: Pod "azurefile-volume-tester-28sgr" satisfied condition "Succeeded or Failed"
Nov  9 11:35:17.071: INFO: deleting Pod "azurefile-3274"/"azurefile-volume-tester-28sgr"
Nov  9 11:35:17.184: INFO: Pod azurefile-volume-tester-28sgr has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-28sgr in namespace azurefile-3274
Nov  9 11:35:17.301: INFO: deleting PVC "azurefile-3274"/"pvc-gx49p"
Nov  9 11:35:17.301: INFO: Deleting PersistentVolumeClaim "pvc-gx49p"
... skipping 33 lines ...
Nov  9 11:35:22.947: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-8h5n7] to have phase Bound
Nov  9 11:35:23.056: INFO: PersistentVolumeClaim pvc-8h5n7 found and phase=Bound (109.658141ms)
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  9 11:35:23.390: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-jhc22" in namespace "azurefile-495" to be "Succeeded or Failed"
Nov  9 11:35:23.500: INFO: Pod "azurefile-volume-tester-jhc22": Phase="Pending", Reason="", readiness=false. Elapsed: 110.101533ms
Nov  9 11:35:25.611: INFO: Pod "azurefile-volume-tester-jhc22": Phase="Pending", Reason="", readiness=false. Elapsed: 2.221752773s
Nov  9 11:35:27.722: INFO: Pod "azurefile-volume-tester-jhc22": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.332254102s
STEP: Saw pod success
Nov  9 11:35:27.722: INFO: Pod "azurefile-volume-tester-jhc22" satisfied condition "Succeeded or Failed"
Nov  9 11:35:27.722: INFO: deleting Pod "azurefile-495"/"azurefile-volume-tester-jhc22"
Nov  9 11:35:27.836: INFO: Pod azurefile-volume-tester-jhc22 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-jhc22 in namespace azurefile-495
Nov  9 11:35:27.954: INFO: deleting PVC "azurefile-495"/"pvc-8h5n7"
Nov  9 11:35:27.954: INFO: Deleting PersistentVolumeClaim "pvc-8h5n7"
... skipping 137 lines ...
Nov  9 11:37:43.845: INFO: PersistentVolumeClaim pvc-gj77b found but phase is Pending instead of Bound.
Nov  9 11:37:45.955: INFO: PersistentVolumeClaim pvc-gj77b found and phase=Bound (1m41.44342873s)
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  9 11:37:46.285: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-brqgm" in namespace "azurefile-5541" to be "Succeeded or Failed"
Nov  9 11:37:46.394: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 109.315466ms
Nov  9 11:37:48.504: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.21949698s
Nov  9 11:37:50.614: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.329702053s
Nov  9 11:37:52.725: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.440735361s
Nov  9 11:37:54.837: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.552434564s
Nov  9 11:37:56.948: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.663275906s
... skipping 7 lines ...
Nov  9 11:38:13.836: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 27.550964246s
Nov  9 11:38:15.948: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.663876081s
Nov  9 11:38:18.059: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 31.774465775s
Nov  9 11:38:20.170: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Pending", Reason="", readiness=false. Elapsed: 33.885290879s
Nov  9 11:38:22.280: INFO: Pod "azurefile-volume-tester-brqgm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.995136993s
STEP: Saw pod success
Nov  9 11:38:22.280: INFO: Pod "azurefile-volume-tester-brqgm" satisfied condition "Succeeded or Failed"
Nov  9 11:38:22.280: INFO: deleting Pod "azurefile-5541"/"azurefile-volume-tester-brqgm"
Nov  9 11:38:22.435: INFO: Pod azurefile-volume-tester-brqgm has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-brqgm in namespace azurefile-5541
Nov  9 11:38:22.555: INFO: deleting PVC "azurefile-5541"/"pvc-gj77b"
Nov  9 11:38:22.555: INFO: Deleting PersistentVolumeClaim "pvc-gj77b"
... skipping 33 lines ...
Nov  9 11:38:26.164: INFO: PersistentVolumeClaim pvc-kjsvw found but phase is Pending instead of Bound.
Nov  9 11:38:28.275: INFO: PersistentVolumeClaim pvc-kjsvw found and phase=Bound (2.21982493s)
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  9 11:38:28.607: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-wzg6r" in namespace "azurefile-5356" to be "Succeeded or Failed"
Nov  9 11:38:28.716: INFO: Pod "azurefile-volume-tester-wzg6r": Phase="Pending", Reason="", readiness=false. Elapsed: 109.483856ms
Nov  9 11:38:30.827: INFO: Pod "azurefile-volume-tester-wzg6r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.22018862s
STEP: Saw pod success
Nov  9 11:38:30.827: INFO: Pod "azurefile-volume-tester-wzg6r" satisfied condition "Succeeded or Failed"
Nov  9 11:38:30.827: INFO: deleting Pod "azurefile-5356"/"azurefile-volume-tester-wzg6r"
Nov  9 11:38:30.941: INFO: Pod azurefile-volume-tester-wzg6r has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-wzg6r in namespace azurefile-5356
Nov  9 11:38:31.056: INFO: deleting PVC "azurefile-5356"/"pvc-kjsvw"
Nov  9 11:38:31.056: INFO: Deleting PersistentVolumeClaim "pvc-kjsvw"
... skipping 129 lines ...
Nov  9 11:40:33.221: INFO: PersistentVolumeClaim pvc-ztkxc found but phase is Pending instead of Bound.
Nov  9 11:40:35.337: INFO: PersistentVolumeClaim pvc-ztkxc found and phase=Bound (27.552319692s)
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
Nov  9 11:40:35.668: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-7lgzv" in namespace "azurefile-4147" to be "Error status code"
Nov  9 11:40:35.778: INFO: Pod "azurefile-volume-tester-7lgzv": Phase="Pending", Reason="", readiness=false. Elapsed: 109.910632ms
Nov  9 11:40:37.889: INFO: Pod "azurefile-volume-tester-7lgzv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.2211037s
Nov  9 11:40:40.000: INFO: Pod "azurefile-volume-tester-7lgzv": Phase="Failed", Reason="", readiness=false. Elapsed: 4.332518974s
STEP: Saw pod failure
Nov  9 11:40:40.000: INFO: Pod "azurefile-volume-tester-7lgzv" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov  9 11:40:40.125: INFO: deleting Pod "azurefile-4147"/"azurefile-volume-tester-7lgzv"
Nov  9 11:40:40.239: INFO: Pod azurefile-volume-tester-7lgzv has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-7lgzv in namespace azurefile-4147
Nov  9 11:40:40.356: INFO: deleting PVC "azurefile-4147"/"pvc-ztkxc"
... skipping 194 lines ...
Nov  9 11:42:53.021: INFO: PersistentVolumeClaim pvc-qt4rd found but phase is Pending instead of Bound.
Nov  9 11:42:55.132: INFO: PersistentVolumeClaim pvc-qt4rd found and phase=Bound (2.219889293s)
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  9 11:42:55.462: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-9dkgq" in namespace "azurefile-5561" to be "Succeeded or Failed"
Nov  9 11:42:55.571: INFO: Pod "azurefile-volume-tester-9dkgq": Phase="Pending", Reason="", readiness=false. Elapsed: 109.527462ms
Nov  9 11:42:57.681: INFO: Pod "azurefile-volume-tester-9dkgq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.21909593s
STEP: Saw pod success
Nov  9 11:42:57.681: INFO: Pod "azurefile-volume-tester-9dkgq" 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
2021/11/09 11:43:28 Running in Prow, converting AZURE_CREDENTIALS to AZURE_CREDENTIAL_FILE
... skipping 40 lines ...
Nov  9 11:43:32.846: INFO: PersistentVolumeClaim pvc-vbjmr found but phase is Pending instead of Bound.
Nov  9 11:43:34.955: INFO: PersistentVolumeClaim pvc-vbjmr found and phase=Bound (2.218364239s)
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  9 11:43:35.284: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-hqjj9" in namespace "azurefile-4376" to be "Succeeded or Failed"
Nov  9 11:43:35.394: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Pending", Reason="", readiness=false. Elapsed: 109.236992ms
Nov  9 11:43:37.505: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.220349158s
Nov  9 11:43:39.616: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.331830288s
Nov  9 11:43:41.727: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.442715169s
Nov  9 11:43:43.838: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.553167979s
Nov  9 11:43:45.948: INFO: Pod "azurefile-volume-tester-hqjj9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.663961927s
STEP: Saw pod success
Nov  9 11:43:45.949: INFO: Pod "azurefile-volume-tester-hqjj9" satisfied condition "Succeeded or Failed"
Nov  9 11:43:45.949: INFO: deleting Pod "azurefile-4376"/"azurefile-volume-tester-hqjj9"
Nov  9 11:43:46.063: INFO: Pod azurefile-volume-tester-hqjj9 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-hqjj9 in namespace azurefile-4376
Nov  9 11:43:46.180: INFO: deleting PVC "azurefile-4376"/"pvc-vbjmr"
Nov  9 11:43:46.180: INFO: Deleting PersistentVolumeClaim "pvc-vbjmr"
... skipping 35 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
Nov  9 11:43:54.422: INFO: deleting Pod "azurefile-1577"/"azurefile-volume-tester-lwgmp"
Nov  9 11:43:54.533: INFO: Error getting logs for pod azurefile-volume-tester-lwgmp: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-lwgmp)
STEP: Deleting pod azurefile-volume-tester-lwgmp in namespace azurefile-1577
Nov  9 11:43:54.645: INFO: deleting PVC "azurefile-1577"/"pvc-46mgw"
Nov  9 11:43:54.645: INFO: Deleting PersistentVolumeClaim "pvc-46mgw"
STEP: waiting for claim's PV "pvc-b9741d82-bfa2-4db3-978b-d6652248aef0" to be deleted
Nov  9 11:43:54.976: INFO: Waiting up to 10m0s for PersistentVolume pvc-b9741d82-bfa2-4db3-978b-d6652248aef0 to get deleted
Nov  9 11:43:55.086: INFO: PersistentVolume pvc-b9741d82-bfa2-4db3-978b-d6652248aef0 found and phase=Bound (109.302086ms)
... skipping 34 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
Nov  9 11:44:13.199: INFO: deleting Pod "azurefile-953"/"azurefile-volume-tester-x5dmq"
Nov  9 11:44:13.312: INFO: Error getting logs for pod azurefile-volume-tester-x5dmq: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-x5dmq)
STEP: Deleting pod azurefile-volume-tester-x5dmq in namespace azurefile-953
Nov  9 11:44:13.433: INFO: deleting PVC "azurefile-953"/"pvc-th9q9"
Nov  9 11:44:13.433: INFO: Deleting PersistentVolumeClaim "pvc-th9q9"
STEP: waiting for claim's PV "pvc-6f8ef2c3-f80c-421d-94ba-0c4af1296919" to be deleted
Nov  9 11:44:13.764: INFO: Waiting up to 10m0s for PersistentVolume pvc-6f8ef2c3-f80c-421d-94ba-0c4af1296919 to get deleted
Nov  9 11:44:13.874: INFO: PersistentVolume pvc-6f8ef2c3-f80c-421d-94ba-0c4af1296919 found and phase=Bound (109.908775ms)
... skipping 116 lines ...
Nov  9 11:46:04.341: INFO: PersistentVolumeClaim pvc-n6nmm found but phase is Pending instead of Bound.
Nov  9 11:46:06.449: INFO: PersistentVolumeClaim pvc-n6nmm found and phase=Bound (2.217225005s)
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
Nov  9 11:46:06.776: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-6h77w" in namespace "azurefile-9336" to be "Error status code"
Nov  9 11:46:06.884: INFO: Pod "azurefile-volume-tester-6h77w": Phase="Pending", Reason="", readiness=false. Elapsed: 107.948929ms
Nov  9 11:46:08.994: INFO: Pod "azurefile-volume-tester-6h77w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217702018s
Nov  9 11:46:11.102: INFO: Pod "azurefile-volume-tester-6h77w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326118578s
Nov  9 11:46:13.212: INFO: Pod "azurefile-volume-tester-6h77w": Phase="Failed", Reason="", readiness=false. Elapsed: 6.435888126s
STEP: Saw pod failure
Nov  9 11:46:13.212: INFO: Pod "azurefile-volume-tester-6h77w" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov  9 11:46:13.333: INFO: deleting Pod "azurefile-9336"/"azurefile-volume-tester-6h77w"
Nov  9 11:46:13.445: INFO: Pod azurefile-volume-tester-6h77w has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-6h77w in namespace azurefile-9336
Nov  9 11:46:13.557: INFO: deleting PVC "azurefile-9336"/"pvc-n6nmm"
... skipping 201 lines ...
Nov  9 11:46:52.072: INFO: PersistentVolumeClaim pvc-xrnwt found but phase is Pending instead of Bound.
Nov  9 11:46:54.181: INFO: PersistentVolumeClaim pvc-xrnwt found and phase=Bound (2.217228699s)
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  9 11:46:54.508: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-cbt29" in namespace "azurefile-8553" to be "Succeeded or Failed"
Nov  9 11:46:54.616: INFO: Pod "azurefile-volume-tester-cbt29": Phase="Pending", Reason="", readiness=false. Elapsed: 108.294305ms
Nov  9 11:46:56.726: INFO: Pod "azurefile-volume-tester-cbt29": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218044615s
Nov  9 11:46:58.838: INFO: Pod "azurefile-volume-tester-cbt29": Phase="Pending", Reason="", readiness=false. Elapsed: 4.329623144s
Nov  9 11:47:00.947: INFO: Pod "azurefile-volume-tester-cbt29": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.438748119s
STEP: Saw pod success
Nov  9 11:47:00.947: INFO: Pod "azurefile-volume-tester-cbt29" satisfied condition "Succeeded or Failed"
Nov  9 11:47:00.947: INFO: deleting Pod "azurefile-8553"/"azurefile-volume-tester-cbt29"
Nov  9 11:47:01.059: INFO: Pod azurefile-volume-tester-cbt29 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-cbt29 in namespace azurefile-8553
Nov  9 11:47:01.176: INFO: deleting PVC "azurefile-8553"/"pvc-xrnwt"
Nov  9 11:47:01.176: INFO: Deleting PersistentVolumeClaim "pvc-xrnwt"
... skipping 74 lines ...
Nov  9 11:47:13.110: INFO: PersistentVolumeClaim pvc-vlm4x found but phase is Pending instead of Bound.
Nov  9 11:47:15.219: INFO: PersistentVolumeClaim pvc-vlm4x found and phase=Bound (2.217733331s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov  9 11:47:15.546: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-6jhcf" in namespace "azurefile-9267" to be "Succeeded or Failed"
Nov  9 11:47:15.654: INFO: Pod "azurefile-volume-tester-6jhcf": Phase="Pending", Reason="", readiness=false. Elapsed: 108.034245ms
Nov  9 11:47:17.764: INFO: Pod "azurefile-volume-tester-6jhcf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217576453s
Nov  9 11:47:19.872: INFO: Pod "azurefile-volume-tester-6jhcf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.325990535s
STEP: Saw pod success
Nov  9 11:47:19.872: INFO: Pod "azurefile-volume-tester-6jhcf" satisfied condition "Succeeded or Failed"
STEP: creating volume snapshot class
STEP: setting up the VolumeSnapshotClass
STEP: creating a VolumeSnapshotClass
STEP: taking snapshots
STEP: creating a VolumeSnapshot for pvc-vlm4x
STEP: waiting for VolumeSnapshot to be ready to use - volume-snapshot-lfjz7
... skipping 31 lines ...
check the driver pods if restarts ...
======================================================================================
2021/11/09 11:47:38 Check successfully
Nov  9 11:47:38.880: INFO: >>> kubeConfig: /root/tmp4077124947/kubeconfig/kubeconfig.westeurope.json
2021/11/09 11:47:38 run script: test/utils/get_storage_account_secret_name.sh
2021/11/09 11:47:39 got output: azure-storage-account-f87f94cfbcc7d4918b5af59-secret
, error: <nil>
2021/11/09 11:47:39 got storage account secret name: azure-storage-account-f87f94cfbcc7d4918b5af59-secret
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: waiting for PVC to be in phase "Bound"
Nov  9 11:47:39.652: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lw5zr] to have phase Bound
Nov  9 11:47:39.761: INFO: PersistentVolumeClaim pvc-lw5zr found and phase=Bound (109.060401ms)
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  9 11:47:40.087: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-vx2s8" in namespace "azurefile-5802" to be "Succeeded or Failed"
Nov  9 11:47:40.195: INFO: Pod "azurefile-volume-tester-vx2s8": Phase="Pending", Reason="", readiness=false. Elapsed: 108.220756ms
Nov  9 11:47:42.305: INFO: Pod "azurefile-volume-tester-vx2s8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.218103948s
STEP: Saw pod success
Nov  9 11:47:42.305: INFO: Pod "azurefile-volume-tester-vx2s8" satisfied condition "Succeeded or Failed"
Nov  9 11:47:42.305: INFO: deleting Pod "azurefile-5802"/"azurefile-volume-tester-vx2s8"
Nov  9 11:47:42.419: INFO: Pod azurefile-volume-tester-vx2s8 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-vx2s8 in namespace azurefile-5802
Nov  9 11:47:42.531: INFO: deleting PVC "azurefile-5802"/"pvc-lw5zr"
Nov  9 11:47:42.531: INFO: Deleting PersistentVolumeClaim "pvc-lw5zr"
... skipping 33 lines ...
Nov  9 11:47:46.355: INFO: PersistentVolumeClaim pvc-2rkbr found but phase is Pending instead of Bound.
Nov  9 11:47:48.464: INFO: PersistentVolumeClaim pvc-2rkbr found and phase=Bound (2.216738913s)
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  9 11:47:48.791: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-7vc2b" in namespace "azurefile-493" to be "Succeeded or Failed"
Nov  9 11:47:48.899: INFO: Pod "azurefile-volume-tester-7vc2b": Phase="Pending", Reason="", readiness=false. Elapsed: 107.882271ms
Nov  9 11:47:51.010: INFO: Pod "azurefile-volume-tester-7vc2b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218747707s
Nov  9 11:47:53.120: INFO: Pod "azurefile-volume-tester-7vc2b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.32853694s
STEP: Saw pod success
Nov  9 11:47:53.120: INFO: Pod "azurefile-volume-tester-7vc2b" satisfied condition "Succeeded or Failed"
Nov  9 11:47:53.120: INFO: deleting Pod "azurefile-493"/"azurefile-volume-tester-7vc2b"
Nov  9 11:47:53.234: INFO: Pod azurefile-volume-tester-7vc2b has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-7vc2b in namespace azurefile-493
Nov  9 11:47:53.349: INFO: deleting PVC "azurefile-493"/"pvc-2rkbr"
Nov  9 11:47:53.349: INFO: Deleting PersistentVolumeClaim "pvc-2rkbr"
... skipping 68 lines ...
check the driver pods if restarts ...
======================================================================================
2021/11/09 11:49:15 Check successfully
Nov  9 11:49:15.007: INFO: >>> kubeConfig: /root/tmp4077124947/kubeconfig/kubeconfig.westeurope.json
2021/11/09 11:49:15 run script: test/utils/get_storage_account_secret_name.sh
2021/11/09 11:49:15 got output: azure-storage-account-f87f94cfbcc7d4918b5af59-secret
, error: <nil>
2021/11/09 11:49:15 got storage account secret name: azure-storage-account-f87f94cfbcc7d4918b5af59-secret
STEP: Successfully provisioned AzureFile volume: "kubetest-b2bnnve2#f87f94cfbcc7d4918b5af59#csi-inline-smb-volume##csi-inline-smb-volume"

STEP: deploying the pod
STEP: checking that the pods command exits with no error
Nov  9 11:49:17.475: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-xvcx9" in namespace "azurefile-2818" to be "Succeeded or Failed"
Nov  9 11:49:17.585: INFO: Pod "azurefile-volume-tester-xvcx9": Phase="Pending", Reason="", readiness=false. Elapsed: 110.155115ms
Nov  9 11:49:19.694: INFO: Pod "azurefile-volume-tester-xvcx9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.219350042s
STEP: Saw pod success
Nov  9 11:49:19.694: INFO: Pod "azurefile-volume-tester-xvcx9" satisfied condition "Succeeded or Failed"
Nov  9 11:49:19.694: INFO: deleting Pod "azurefile-2818"/"azurefile-volume-tester-xvcx9"
Nov  9 11:49:19.849: INFO: Pod azurefile-volume-tester-xvcx9 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-xvcx9 in namespace azurefile-2818
Nov  9 11:49:19.972: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azurefile-2818" for this suite.
... skipping 40 lines ...
check the driver pods if restarts ...
======================================================================================
2021/11/09 11:49:24 Check successfully
Nov  9 11:49:24.937: INFO: >>> kubeConfig: /root/tmp4077124947/kubeconfig/kubeconfig.westeurope.json
STEP: creating secret smbcreds in namespace azurefile-5786
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Nov  9 11:49:25.160: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-hflb6" in namespace "azurefile-5786" to be "Succeeded or Failed"
Nov  9 11:49:25.268: INFO: Pod "azurefile-volume-tester-hflb6": Phase="Pending", Reason="", readiness=false. Elapsed: 107.948488ms
Nov  9 11:49:27.377: INFO: Pod "azurefile-volume-tester-hflb6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.21708035s
STEP: Saw pod success
Nov  9 11:49:27.377: INFO: Pod "azurefile-volume-tester-hflb6" satisfied condition "Succeeded or Failed"
Nov  9 11:49:27.377: INFO: deleting Pod "azurefile-5786"/"azurefile-volume-tester-hflb6"
Nov  9 11:49:27.489: INFO: Pod azurefile-volume-tester-hflb6 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-hflb6 in namespace azurefile-5786
Nov  9 11:49:27.608: INFO: deleting Secret smbcreds
Nov  9 11:49:27.718: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 28 lines ...