This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: always enable csi-snapshotter in helm install
ResultABORTED
Tests 0 failed / 31 succeeded
Started2021-07-09 09:20
Elapsed32m9s
Revision58e2203179f90ed2fff7d6e9f3ce6060e178726f
Refs 737

No Test Failures!


Show 31 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 69 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   215k      0 --:--:-- --:--:-- --:--:--  215k
Downloading https://get.helm.sh/helm-v3.6.2-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azurefile-csi:e2e-63bb9d56a343ffe9d08387ec33e9ed2dc7ff7591 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azurefile-csi:e2e-63bb9d56a343ffe9d08387ec33e9ed2dc7ff7591 not found: manifest unknown: manifest tagged by "e2e-63bb9d56a343ffe9d08387ec33e9ed2dc7ff7591" 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-63bb9d56a343ffe9d08387ec33e9ed2dc7ff7591 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=63bb9d56a343ffe9d08387ec33e9ed2dc7ff7591 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2021-07-09T09:26:50Z -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 662 lines ...
#9 9.197 debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
#9 9.197 debconf: falling back to frontend: Teletype
#9 9.228 Setting up libnfsidmap2:amd64 (0.25-5.1) ...
#9 9.240 Setting up python (2.7.16-1) ...
#9 9.261 Setting up nfs-common (1:1.3.4-2.5+deb10u1) ...
#9 9.283 /var/lib/dpkg/info/nfs-common.postinst: 7: /var/lib/dpkg/info/nfs-common.postinst: ucf: not found
#9 9.284 dpkg: error processing package nfs-common (--configure):

#9 9.284  installed nfs-common package post-installation script subprocess returned error exit status 127

#9 9.284 Processing triggers for libc-bin (2.28-10) ...
#9 9.305 Processing triggers for mime-support (3.62) ...
#9 9.336 Errors were encountered while processing:
#9 9.336  nfs-common
#9 9.356 E: Sub-process /usr/bin/dpkg returned an error code (1)
#9 DONE 9.5s

#10 exporting to image
#10 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
#10 exporting layers
#10 exporting layers 6.4s done
... skipping 562 lines ...
#8 48.69 debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/aarch64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
#8 48.69 debconf: falling back to frontend: Teletype
#8 49.06 Setting up libnfsidmap2:arm64 (0.25-5.1) ...
#8 49.07 Setting up python (2.7.16-1) ...
#8 49.33 Setting up nfs-common (1:1.3.4-2.5+deb10u1) ...
#8 49.39 /var/lib/dpkg/info/nfs-common.postinst: 7: /var/lib/dpkg/info/nfs-common.postinst: ucf: not found
#8 49.39 dpkg: error processing package nfs-common (--configure):

#8 49.39  installed nfs-common package post-installation script subprocess returned error exit status 127

#8 49.40 Processing triggers for libc-bin (2.28-10) ...
#8 49.50 Processing triggers for mime-support (3.62) ...
#8 49.87 Errors were encountered while processing:
#8 49.87  nfs-common
#8 49.99 E: Sub-process /usr/bin/dpkg returned an error code (1)
#8 DONE 50.1s

#9 exporting to image
#9 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
#9 exporting layers
#9 exporting layers 6.1s done
... skipping 745 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 789 lines ...
        - name: csi-resizer
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.1.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - '-handle-volume-inuse-error=false'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: socket-dir
... skipping 186 lines ...
Git Commit: N/A
Go Version: go1.16.5
Platform: linux/amd64

Streaming logs below:
STEP: Building a namespace api object, basename azurefile
E0709 09:36:54.510543   14058 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0709 09:36:54.513374   14058 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME
I0709 09:36:54.513399   14058 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0709 09:36:54.513404   14058 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0709 09:36:54.513408   14058 driver.go:93] Enabling controller service capability: EXPAND_VOLUME
I0709 09:36:54.513413   14058 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER
I0709 09:36:54.513418   14058 driver.go:112] Enabling volume access mode: SINGLE_NODE_READER_ONLY
... skipping 19 lines ...
Jul  9 09:37:20.816: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-s6lj8] to have phase Bound
Jul  9 09:37:20.917: INFO: PersistentVolumeClaim pvc-s6lj8 found and phase=Bound (101.057005ms)
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
Jul  9 09:37:21.221: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-sr6mj" in namespace "azurefile-8081" to be "Error status code"
Jul  9 09:37:21.321: INFO: Pod "azurefile-volume-tester-sr6mj": Phase="Pending", Reason="", readiness=false. Elapsed: 100.177771ms
Jul  9 09:37:23.423: INFO: Pod "azurefile-volume-tester-sr6mj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.202199418s
Jul  9 09:37:25.526: INFO: Pod "azurefile-volume-tester-sr6mj": Phase="Failed", Reason="", readiness=false. Elapsed: 4.305383319s
STEP: Saw pod failure
Jul  9 09:37:25.526: INFO: Pod "azurefile-volume-tester-sr6mj" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul  9 09:37:25.672: INFO: deleting Pod "azurefile-8081"/"azurefile-volume-tester-sr6mj"
Jul  9 09:37:25.776: INFO: Pod azurefile-volume-tester-sr6mj has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-sr6mj in namespace azurefile-8081
Jul  9 09:37:25.884: INFO: deleting PVC "azurefile-8081"/"pvc-s6lj8"
... skipping 37 lines ...
Jul  9 09:37:29.633: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-hz54c] to have phase Bound
Jul  9 09:37:29.733: INFO: PersistentVolumeClaim pvc-hz54c found and phase=Bound (100.170199ms)
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
Jul  9 09:37:30.035: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-sj62w" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:30.135: INFO: Pod "azurefile-volume-tester-sj62w": Phase="Pending", Reason="", readiness=false. Elapsed: 99.774841ms
Jul  9 09:37:32.237: INFO: Pod "azurefile-volume-tester-sj62w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.202276532s
Jul  9 09:37:34.340: INFO: Pod "azurefile-volume-tester-sj62w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.30450134s
STEP: Saw pod success
Jul  9 09:37:34.340: INFO: Pod "azurefile-volume-tester-sj62w" 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"
Jul  9 09:37:34.543: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-d7nfg] to have phase Bound
Jul  9 09:37:34.643: INFO: PersistentVolumeClaim pvc-d7nfg found and phase=Bound (100.133893ms)
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
Jul  9 09:37:34.946: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-5wx9p" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:35.047: INFO: Pod "azurefile-volume-tester-5wx9p": Phase="Pending", Reason="", readiness=false. Elapsed: 101.009109ms
Jul  9 09:37:37.149: INFO: Pod "azurefile-volume-tester-5wx9p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.202388558s
Jul  9 09:37:39.254: INFO: Pod "azurefile-volume-tester-5wx9p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.307344836s
STEP: Saw pod success
Jul  9 09:37:39.254: INFO: Pod "azurefile-volume-tester-5wx9p" 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"
Jul  9 09:37:39.458: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-k6xgh] to have phase Bound
Jul  9 09:37:39.563: INFO: PersistentVolumeClaim pvc-k6xgh found and phase=Bound (105.731938ms)
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
Jul  9 09:37:39.867: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-nqqtt" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:39.968: INFO: Pod "azurefile-volume-tester-nqqtt": Phase="Pending", Reason="", readiness=false. Elapsed: 100.721111ms
Jul  9 09:37:42.068: INFO: Pod "azurefile-volume-tester-nqqtt": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.200992138s
STEP: Saw pod success
Jul  9 09:37:42.068: INFO: Pod "azurefile-volume-tester-nqqtt" 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"
Jul  9 09:37:42.275: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-9r9lp] to have phase Bound
Jul  9 09:37:42.376: INFO: PersistentVolumeClaim pvc-9r9lp found and phase=Bound (101.203518ms)
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
Jul  9 09:37:42.680: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-x2cst" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:42.782: INFO: Pod "azurefile-volume-tester-x2cst": Phase="Pending", Reason="", readiness=false. Elapsed: 101.909643ms
Jul  9 09:37:44.883: INFO: Pod "azurefile-volume-tester-x2cst": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.203324302s
STEP: Saw pod success
Jul  9 09:37:44.884: INFO: Pod "azurefile-volume-tester-x2cst" 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"
Jul  9 09:37:45.088: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5rw4z] to have phase Bound
Jul  9 09:37:45.188: INFO: PersistentVolumeClaim pvc-5rw4z found and phase=Bound (99.537578ms)
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
Jul  9 09:37:45.491: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-cntdx" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:45.592: INFO: Pod "azurefile-volume-tester-cntdx": Phase="Pending", Reason="", readiness=false. Elapsed: 100.813032ms
Jul  9 09:37:47.694: INFO: Pod "azurefile-volume-tester-cntdx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.202970924s
Jul  9 09:37:49.796: INFO: Pod "azurefile-volume-tester-cntdx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.30537322s
STEP: Saw pod success
Jul  9 09:37:49.796: INFO: Pod "azurefile-volume-tester-cntdx" 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"
Jul  9 09:37:49.999: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-lm8k9] to have phase Bound
Jul  9 09:37:50.099: INFO: PersistentVolumeClaim pvc-lm8k9 found and phase=Bound (100.131864ms)
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
Jul  9 09:37:50.402: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-vmpwq" in namespace "azurefile-1318" to be "Succeeded or Failed"
Jul  9 09:37:50.502: INFO: Pod "azurefile-volume-tester-vmpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 100.002503ms
Jul  9 09:37:52.602: INFO: Pod "azurefile-volume-tester-vmpwq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.200405264s
Jul  9 09:37:54.704: INFO: Pod "azurefile-volume-tester-vmpwq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.301666393s
STEP: Saw pod success
Jul  9 09:37:54.704: INFO: Pod "azurefile-volume-tester-vmpwq" satisfied condition "Succeeded or Failed"
Jul  9 09:37:54.704: INFO: deleting Pod "azurefile-1318"/"azurefile-volume-tester-vmpwq"
Jul  9 09:37:54.817: INFO: Pod azurefile-volume-tester-vmpwq has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-vmpwq in namespace azurefile-1318
Jul  9 09:37:54.923: INFO: deleting PVC "azurefile-1318"/"pvc-lm8k9"
Jul  9 09:37:54.923: INFO: Deleting PersistentVolumeClaim "pvc-lm8k9"
... skipping 143 lines ...
Jul  9 09:38:05.992: INFO: PersistentVolumeClaim pvc-wbfvz found but phase is Pending instead of Bound.
Jul  9 09:38:08.093: INFO: PersistentVolumeClaim pvc-wbfvz found and phase=Bound (2.200347328s)
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
Jul  9 09:38:08.413: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-bnf9l" in namespace "azurefile-3274" to be "Succeeded or Failed"
Jul  9 09:38:08.513: INFO: Pod "azurefile-volume-tester-bnf9l": Phase="Pending", Reason="", readiness=false. Elapsed: 99.946713ms
Jul  9 09:38:10.616: INFO: Pod "azurefile-volume-tester-bnf9l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.202604965s
STEP: Saw pod success
Jul  9 09:38:10.616: INFO: Pod "azurefile-volume-tester-bnf9l" satisfied condition "Succeeded or Failed"
Jul  9 09:38:10.616: INFO: deleting Pod "azurefile-3274"/"azurefile-volume-tester-bnf9l"
Jul  9 09:38:10.720: INFO: Pod azurefile-volume-tester-bnf9l has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-bnf9l in namespace azurefile-3274
Jul  9 09:38:10.825: INFO: deleting PVC "azurefile-3274"/"pvc-wbfvz"
Jul  9 09:38:10.825: INFO: Deleting PersistentVolumeClaim "pvc-wbfvz"
... skipping 33 lines ...
Jul  9 09:38:14.460: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-vxxxw] to have phase Bound
Jul  9 09:38:14.560: INFO: PersistentVolumeClaim pvc-vxxxw found and phase=Bound (100.39814ms)
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
Jul  9 09:38:14.865: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-tqjpg" in namespace "azurefile-495" to be "Succeeded or Failed"
Jul  9 09:38:14.967: INFO: Pod "azurefile-volume-tester-tqjpg": Phase="Pending", Reason="", readiness=false. Elapsed: 102.229219ms
Jul  9 09:38:17.068: INFO: Pod "azurefile-volume-tester-tqjpg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.203700105s
Jul  9 09:38:19.169: INFO: Pod "azurefile-volume-tester-tqjpg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.304502809s
STEP: Saw pod success
Jul  9 09:38:19.169: INFO: Pod "azurefile-volume-tester-tqjpg" satisfied condition "Succeeded or Failed"
Jul  9 09:38:19.169: INFO: deleting Pod "azurefile-495"/"azurefile-volume-tester-tqjpg"
Jul  9 09:38:19.274: INFO: Pod azurefile-volume-tester-tqjpg has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-tqjpg in namespace azurefile-495
Jul  9 09:38:19.382: INFO: deleting PVC "azurefile-495"/"pvc-vxxxw"
Jul  9 09:38:19.382: INFO: Deleting PersistentVolumeClaim "pvc-vxxxw"
... skipping 94 lines ...