This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: skip chmod if mountPermissions is 0 after mount
ResultABORTED
Tests 0 failed / 31 succeeded
Started2022-05-05 12:32
Elapsed48m37s
Revisionaa8356a69b0e75d85ace9f174c3daef7eeaa3680
Refs 1011

No Test Failures!


Show 31 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 670 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 131 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-vc6l0h-kubeconfig; do sleep 1; done"
capz-vc6l0h-kubeconfig                 cluster.x-k8s.io/secret               1      0s
# Get kubeconfig and store it locally.
kubectl get secrets capz-vc6l0h-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-vc6l0h-control-plane-9598z   NotReady   control-plane,master   12s   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-vc6l0h-control-plane-9598z condition met
node/capz-vc6l0h-md-0-dcw92 condition met
... skipping 35 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   217k      0 --:--:-- --:--:-- --:--:--  213k
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-20df2f81f6931e6c81dd9806cf79cf30b00d64ed || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-20df2f81f6931e6c81dd9806cf79cf30b00d64ed not found: manifest unknown: manifest tagged by "e2e-20df2f81f6931e6c81dd9806cf79cf30b00d64ed" 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-20df2f81f6931e6c81dd9806cf79cf30b00d64ed -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=20df2f81f6931e6c81dd9806cf79cf30b00d64ed -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-05-05T12:44: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 1812 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
W0505 12:57:37.913165   35901 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
I0505 12:57:37.914154   35901 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME
I0505 12:57:37.914179   35901 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0505 12:57:37.914183   35901 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0505 12:57:37.914188   35901 driver.go:93] Enabling controller service capability: EXPAND_VOLUME
I0505 12:57:37.914191   35901 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER
I0505 12:57:37.914199   35901 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER
... skipping 120 lines ...
May  5 12:59:41.492: INFO: PersistentVolumeClaim pvc-n546c found but phase is Pending instead of Bound.
May  5 12:59:43.528: INFO: PersistentVolumeClaim pvc-n546c found and phase=Bound (1m37.82776643s)
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  5 12:59:43.635: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-8ds6g" in namespace "azurefile-2540" to be "Succeeded or Failed"
May  5 12:59:43.676: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 40.037219ms
May  5 12:59:45.713: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077708888s
May  5 12:59:47.749: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.113864325s
May  5 12:59:49.786: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.150636979s
May  5 12:59:51.822: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.18675145s
May  5 12:59:53.859: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.223643202s
... skipping 12 lines ...
May  5 13:00:20.353: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 36.71761343s
May  5 13:00:22.389: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 38.753728005s
May  5 13:00:24.426: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 40.790776833s
May  5 13:00:26.465: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Pending", Reason="", readiness=false. Elapsed: 42.829799569s
May  5 13:00:28.504: INFO: Pod "azurefile-volume-tester-8ds6g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 44.86860256s
STEP: Saw pod success
May  5 13:00:28.504: INFO: Pod "azurefile-volume-tester-8ds6g" satisfied condition "Succeeded or Failed"
May  5 13:00:28.504: INFO: deleting Pod "azurefile-2540"/"azurefile-volume-tester-8ds6g"
May  5 13:00:28.555: INFO: Pod azurefile-volume-tester-8ds6g has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-8ds6g in namespace azurefile-2540
May  5 13:00:28.605: INFO: deleting PVC "azurefile-2540"/"pvc-n546c"
May  5 13:00:28.605: INFO: Deleting PersistentVolumeClaim "pvc-n546c"
... skipping 44 lines ...
May  5 13:00:53.119: INFO: PersistentVolumeClaim pvc-qtl2d found but phase is Pending instead of Bound.
May  5 13:00:55.155: INFO: PersistentVolumeClaim pvc-qtl2d found and phase=Bound (20.415525312s)
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  5 13:00:55.264: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-svr57" in namespace "azurefile-4728" to be "Succeeded or Failed"
May  5 13:00:55.299: INFO: Pod "azurefile-volume-tester-svr57": Phase="Pending", Reason="", readiness=false. Elapsed: 35.377163ms
May  5 13:00:57.337: INFO: Pod "azurefile-volume-tester-svr57": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.07368383s
STEP: Saw pod success
May  5 13:00:57.337: INFO: Pod "azurefile-volume-tester-svr57" satisfied condition "Succeeded or Failed"
May  5 13:00:57.337: INFO: deleting Pod "azurefile-4728"/"azurefile-volume-tester-svr57"
May  5 13:00:57.374: INFO: Pod azurefile-volume-tester-svr57 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-svr57 in namespace azurefile-4728
May  5 13:00:57.422: INFO: deleting PVC "azurefile-4728"/"pvc-qtl2d"
May  5 13:00:57.422: INFO: Deleting PersistentVolumeClaim "pvc-qtl2d"
... skipping 128 lines ...
May  5 13:02:47.239: INFO: PersistentVolumeClaim pvc-xvq6s found but phase is Pending instead of Bound.
May  5 13:02:49.276: INFO: PersistentVolumeClaim pvc-xvq6s found and phase=Bound (20.406113123s)
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  5 13:02:49.385: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-s4rwq" in namespace "azurefile-2790" to be "Error status code"
May  5 13:02:49.421: INFO: Pod "azurefile-volume-tester-s4rwq": Phase="Pending", Reason="", readiness=false. Elapsed: 36.0578ms
May  5 13:02:51.460: INFO: Pod "azurefile-volume-tester-s4rwq": Phase="Failed", Reason="", readiness=false. Elapsed: 2.074866571s
STEP: Saw pod failure
May  5 13:02:51.460: INFO: Pod "azurefile-volume-tester-s4rwq" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May  5 13:02:51.497: INFO: deleting Pod "azurefile-2790"/"azurefile-volume-tester-s4rwq"
May  5 13:02:51.535: INFO: Pod azurefile-volume-tester-s4rwq has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-s4rwq in namespace azurefile-2790
May  5 13:02:51.582: INFO: deleting PVC "azurefile-2790"/"pvc-xvq6s"
... skipping 192 lines ...
May  5 13:04:48.959: INFO: PersistentVolumeClaim pvc-dnqqv found but phase is Pending instead of Bound.
May  5 13:04:50.996: INFO: PersistentVolumeClaim pvc-dnqqv found and phase=Bound (2.072587414s)
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  5 13:04:51.112: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-g2979" in namespace "azurefile-4538" to be "Succeeded or Failed"
May  5 13:04:51.148: INFO: Pod "azurefile-volume-tester-g2979": Phase="Pending", Reason="", readiness=false. Elapsed: 36.627224ms
May  5 13:04:53.186: INFO: Pod "azurefile-volume-tester-g2979": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074531593s
May  5 13:04:55.225: INFO: Pod "azurefile-volume-tester-g2979": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.113405638s
STEP: Saw pod success
May  5 13:04:55.225: INFO: Pod "azurefile-volume-tester-g2979" 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  5 13:05:25.796: INFO: deleting Pod "azurefile-4538"/"azurefile-volume-tester-g2979"
... skipping 40 lines ...
May  5 13:05:31.966: INFO: PersistentVolumeClaim pvc-k9lq4 found but phase is Pending instead of Bound.
May  5 13:05:34.003: INFO: PersistentVolumeClaim pvc-k9lq4 found and phase=Bound (2.073009472s)
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  5 13:05:34.112: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-mm29d" in namespace "azurefile-8266" to be "Succeeded or Failed"
May  5 13:05:34.147: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 35.031803ms
May  5 13:05:36.185: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072726856s
May  5 13:05:38.221: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109628306s
May  5 13:05:40.258: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.146619008s
May  5 13:05:42.296: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 8.183944365s
May  5 13:05:44.332: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 10.22037972s
May  5 13:05:46.371: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Pending", Reason="", readiness=false. Elapsed: 12.259191846s
May  5 13:05:48.409: INFO: Pod "azurefile-volume-tester-mm29d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.297416628s
STEP: Saw pod success
May  5 13:05:48.409: INFO: Pod "azurefile-volume-tester-mm29d" satisfied condition "Succeeded or Failed"
May  5 13:05:48.409: INFO: deleting Pod "azurefile-8266"/"azurefile-volume-tester-mm29d"
May  5 13:05:48.450: INFO: Pod azurefile-volume-tester-mm29d has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-mm29d in namespace azurefile-8266
May  5 13:05:48.499: INFO: deleting PVC "azurefile-8266"/"pvc-k9lq4"
May  5 13:05:48.499: INFO: Deleting PersistentVolumeClaim "pvc-k9lq4"
... skipping 37 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  5 13:05:58.769: INFO: deleting Pod "azurefile-4376"/"azurefile-volume-tester-fd56r"
May  5 13:05:58.807: INFO: Error getting logs for pod azurefile-volume-tester-fd56r: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-fd56r)
STEP: Deleting pod azurefile-volume-tester-fd56r in namespace azurefile-4376
May  5 13:05:58.851: INFO: deleting PVC "azurefile-4376"/"pvc-6h5wc"
May  5 13:05:58.851: INFO: Deleting PersistentVolumeClaim "pvc-6h5wc"
STEP: waiting for claim's PV "pvc-0a6bb62d-11a9-41b5-9805-fdfa9d00628d" to be deleted
May  5 13:05:58.979: INFO: Waiting up to 10m0s for PersistentVolume pvc-0a6bb62d-11a9-41b5-9805-fdfa9d00628d to get deleted
May  5 13:05:59.016: INFO: PersistentVolume pvc-0a6bb62d-11a9-41b5-9805-fdfa9d00628d found and phase=Bound (36.805662ms)
... skipping 58 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  5 13:08:10.292: INFO: deleting Pod "azurefile-7996"/"azurefile-volume-tester-rgvlf"
May  5 13:08:10.336: INFO: Error getting logs for pod azurefile-volume-tester-rgvlf: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-rgvlf)
STEP: Deleting pod azurefile-volume-tester-rgvlf in namespace azurefile-7996
May  5 13:08:10.374: INFO: deleting PVC "azurefile-7996"/"pvc-gjkz6"
May  5 13:08:10.374: INFO: Deleting PersistentVolumeClaim "pvc-gjkz6"
STEP: waiting for claim's PV "pvc-0b14daed-1148-4f2c-b67d-4c378619223f" to be deleted
May  5 13:08:10.487: INFO: Waiting up to 10m0s for PersistentVolume pvc-0b14daed-1148-4f2c-b67d-4c378619223f to get deleted
May  5 13:08:10.540: INFO: PersistentVolume pvc-0b14daed-1148-4f2c-b67d-4c378619223f found and phase=Bound (52.795825ms)
... skipping 140 lines ...
May  5 13:11:41.907: INFO: PersistentVolumeClaim pvc-z9tsv found but phase is Pending instead of Bound.
May  5 13:11:43.944: INFO: PersistentVolumeClaim pvc-z9tsv found and phase=Bound (2.072395889s)
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  5 13:11:44.053: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-9k4mc" in namespace "azurefile-2546" to be "Error status code"
May  5 13:11:44.088: INFO: Pod "azurefile-volume-tester-9k4mc": Phase="Pending", Reason="", readiness=false. Elapsed: 34.662383ms
May  5 13:11:46.126: INFO: Pod "azurefile-volume-tester-9k4mc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073036838s
May  5 13:11:48.165: INFO: Pod "azurefile-volume-tester-9k4mc": Phase="Failed", Reason="", readiness=false. Elapsed: 4.111464505s
STEP: Saw pod failure
May  5 13:11:48.165: INFO: Pod "azurefile-volume-tester-9k4mc" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May  5 13:11:48.203: INFO: deleting Pod "azurefile-2546"/"azurefile-volume-tester-9k4mc"
May  5 13:11:48.240: INFO: Pod azurefile-volume-tester-9k4mc has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azurefile-volume-tester-9k4mc in namespace azurefile-2546
May  5 13:11:48.290: INFO: deleting PVC "azurefile-2546"/"pvc-z9tsv"
... skipping 198 lines ...
May  5 13:12:17.868: INFO: PersistentVolumeClaim pvc-5wvqt found but phase is Pending instead of Bound.
May  5 13:12:19.904: INFO: PersistentVolumeClaim pvc-5wvqt found and phase=Bound (2.071511542s)
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  5 13:12:20.025: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-8kpxf" in namespace "azurefile-7726" to be "Succeeded or Failed"
May  5 13:12:20.061: INFO: Pod "azurefile-volume-tester-8kpxf": Phase="Pending", Reason="", readiness=false. Elapsed: 36.651145ms
May  5 13:12:22.099: INFO: Pod "azurefile-volume-tester-8kpxf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074338582s
May  5 13:12:24.138: INFO: Pod "azurefile-volume-tester-8kpxf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.113742186s
STEP: Saw pod success
May  5 13:12:24.138: INFO: Pod "azurefile-volume-tester-8kpxf" satisfied condition "Succeeded or Failed"
May  5 13:12:24.138: INFO: deleting Pod "azurefile-7726"/"azurefile-volume-tester-8kpxf"
May  5 13:12:24.176: INFO: Pod azurefile-volume-tester-8kpxf has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-8kpxf in namespace azurefile-7726
May  5 13:12:24.226: INFO: deleting PVC "azurefile-7726"/"pvc-5wvqt"
May  5 13:12:24.226: INFO: Deleting PersistentVolumeClaim "pvc-5wvqt"
... skipping 80 lines ...
May  5 13:12:56.598: INFO: PersistentVolumeClaim pvc-hcjw5 found but phase is Pending instead of Bound.
May  5 13:12:58.633: INFO: PersistentVolumeClaim pvc-hcjw5 found and phase=Bound (2.070689351s)
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
May  5 13:12:58.740: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-q9fd7" in namespace "azurefile-3086" to be "Succeeded or Failed"
May  5 13:12:58.776: INFO: Pod "azurefile-volume-tester-q9fd7": Phase="Pending", Reason="", readiness=false. Elapsed: 36.117377ms
May  5 13:13:00.815: INFO: Pod "azurefile-volume-tester-q9fd7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.074519541s
STEP: Saw pod success
May  5 13:13:00.815: INFO: Pod "azurefile-volume-tester-q9fd7" 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-hcjw5
STEP: waiting for VolumeSnapshot to be ready to use - volume-snapshot-pl6jb
... skipping 33 lines ...
check the driver pods if restarts ...
======================================================================================
2022/05/05 13:13:22 Check successfully
May  5 13:13:22.003: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
2022/05/05 13:13:22 run script: test/utils/get_storage_account_secret_name.sh
2022/05/05 13:13:22 got output: azure-storage-account-fcfaf9709da16425eacd075-secret
, error: <nil>
2022/05/05 13:13:22 got storage account secret name: azure-storage-account-fcfaf9709da16425eacd075-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"
May  5 13:13:22.338: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-l8p89] to have phase Bound
May  5 13:13:22.373: INFO: PersistentVolumeClaim pvc-l8p89 found but phase is Pending instead of Bound.
May  5 13:13:24.411: INFO: PersistentVolumeClaim pvc-l8p89 found and phase=Bound (2.072775118s)
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  5 13:13:24.520: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-4qkqf" in namespace "azurefile-1387" to be "Succeeded or Failed"
May  5 13:13:24.555: INFO: Pod "azurefile-volume-tester-4qkqf": Phase="Pending", Reason="", readiness=false. Elapsed: 35.294854ms
May  5 13:13:26.594: INFO: Pod "azurefile-volume-tester-4qkqf": Phase="Running", Reason="", readiness=true. Elapsed: 2.074223222s
May  5 13:13:28.633: INFO: Pod "azurefile-volume-tester-4qkqf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.113700333s
STEP: Saw pod success
May  5 13:13:28.633: INFO: Pod "azurefile-volume-tester-4qkqf" satisfied condition "Succeeded or Failed"
May  5 13:13:28.633: INFO: deleting Pod "azurefile-1387"/"azurefile-volume-tester-4qkqf"
May  5 13:13:28.680: INFO: Pod azurefile-volume-tester-4qkqf has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-4qkqf in namespace azurefile-1387
May  5 13:13:28.729: INFO: deleting PVC "azurefile-1387"/"pvc-l8p89"
May  5 13:13:28.729: INFO: Deleting PersistentVolumeClaim "pvc-l8p89"
... skipping 45 lines ...
May  5 13:13:55.121: INFO: PersistentVolumeClaim pvc-p7n5x found but phase is Pending instead of Bound.
May  5 13:13:57.157: INFO: PersistentVolumeClaim pvc-p7n5x found and phase=Bound (22.440321963s)
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  5 13:13:57.265: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-25gx9" in namespace "azurefile-4547" to be "Succeeded or Failed"
May  5 13:13:57.309: INFO: Pod "azurefile-volume-tester-25gx9": Phase="Pending", Reason="", readiness=false. Elapsed: 44.247683ms
May  5 13:13:59.353: INFO: Pod "azurefile-volume-tester-25gx9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.088250379s
May  5 13:14:01.399: INFO: Pod "azurefile-volume-tester-25gx9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.133802953s
STEP: Saw pod success
May  5 13:14:01.399: INFO: Pod "azurefile-volume-tester-25gx9" satisfied condition "Succeeded or Failed"
May  5 13:14:01.399: INFO: deleting Pod "azurefile-4547"/"azurefile-volume-tester-25gx9"
May  5 13:14:01.436: INFO: Pod azurefile-volume-tester-25gx9 has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-25gx9 in namespace azurefile-4547
May  5 13:14:01.488: INFO: deleting PVC "azurefile-4547"/"pvc-p7n5x"
May  5 13:14:01.488: INFO: Deleting PersistentVolumeClaim "pvc-p7n5x"
... skipping 70 lines ...
check the driver pods if restarts ...
======================================================================================
2022/05/05 13:15:19 Check successfully
May  5 13:15:19.920: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
2022/05/05 13:15:19 run script: test/utils/get_storage_account_secret_name.sh
2022/05/05 13:15:20 got output: azure-storage-account-fcfaf9709da16425eacd075-secret
, error: <nil>
2022/05/05 13:15:20 got storage account secret name: azure-storage-account-fcfaf9709da16425eacd075-secret
STEP: Successfully provisioned AzureFile volume: "capz-vc6l0h#fcfaf9709da16425eacd075#csi-inline-smb-volume##csi-inline-smb-volume#azurefile-4801"

STEP: deploying the pod
STEP: checking that the pods command exits with no error
May  5 13:15:21.219: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-g7mtn" in namespace "azurefile-4801" to be "Succeeded or Failed"
May  5 13:15:21.254: INFO: Pod "azurefile-volume-tester-g7mtn": Phase="Pending", Reason="", readiness=false. Elapsed: 34.997775ms
May  5 13:15:23.297: INFO: Pod "azurefile-volume-tester-g7mtn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.078060308s
STEP: Saw pod success
May  5 13:15:23.297: INFO: Pod "azurefile-volume-tester-g7mtn" satisfied condition "Succeeded or Failed"
May  5 13:15:23.297: INFO: deleting Pod "azurefile-4801"/"azurefile-volume-tester-g7mtn"
May  5 13:15:23.336: INFO: Pod azurefile-volume-tester-g7mtn has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-g7mtn in namespace azurefile-4801
May  5 13:15:23.387: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azurefile-4801" for this suite.
... skipping 37 lines ...
check the driver pods if restarts ...
======================================================================================
2022/05/05 13:15:24 Check successfully
May  5 13:15:24.728: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: creating secret smbcreds in namespace azurefile-1166
STEP: deploying the pod
STEP: checking that the pods command exits with no error
May  5 13:15:24.804: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-ljfsw" in namespace "azurefile-1166" to be "Succeeded or Failed"
May  5 13:15:24.848: INFO: Pod "azurefile-volume-tester-ljfsw": Phase="Pending", Reason="", readiness=false. Elapsed: 43.929583ms
May  5 13:15:26.887: INFO: Pod "azurefile-volume-tester-ljfsw": Phase="Running", Reason="", readiness=true. Elapsed: 2.082728802s
May  5 13:15:28.926: INFO: Pod "azurefile-volume-tester-ljfsw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.121514503s
STEP: Saw pod success
May  5 13:15:28.926: INFO: Pod "azurefile-volume-tester-ljfsw" satisfied condition "Succeeded or Failed"
May  5 13:15:28.926: INFO: deleting Pod "azurefile-1166"/"azurefile-volume-tester-ljfsw"
May  5 13:15:28.974: INFO: Pod azurefile-volume-tester-ljfsw has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-ljfsw in namespace azurefile-1166
May  5 13:15:29.017: INFO: deleting Secret smbcreds
May  5 13:15:29.053: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 52 lines ...
May  5 13:16:20.820: INFO: PersistentVolumeClaim pvc-c8xl6 found but phase is Pending instead of Bound.
May  5 13:16:22.857: INFO: PersistentVolumeClaim pvc-c8xl6 found and phase=Bound (53.002237553s)
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  5 13:16:22.965: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-stt4t" in namespace "azurefile-4415" to be "Succeeded or Failed"
May  5 13:16:23.000: INFO: Pod "azurefile-volume-tester-stt4t": Phase="Pending", Reason="", readiness=false. Elapsed: 35.230082ms
May  5 13:16:25.038: INFO: Pod "azurefile-volume-tester-stt4t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07268551s
May  5 13:16:27.075: INFO: Pod "azurefile-volume-tester-stt4t": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.110470507s
STEP: Saw pod success
May  5 13:16:27.075: INFO: Pod "azurefile-volume-tester-stt4t" satisfied condition "Succeeded or Failed"
May  5 13:16:27.075: INFO: deleting Pod "azurefile-4415"/"azurefile-volume-tester-stt4t"
May  5 13:16:27.115: INFO: Pod azurefile-volume-tester-stt4t has the following logs: hello world

STEP: Deleting pod azurefile-volume-tester-stt4t in namespace azurefile-4415
May  5 13:16:27.162: INFO: deleting PVC "azurefile-4415"/"pvc-c8xl6"
May  5 13:16:27.162: INFO: Deleting PersistentVolumeClaim "pvc-c8xl6"
... skipping 80 lines ...
May  5 13:18:04.876: INFO: PersistentVolumeClaim pvc-gvhgz found but phase is Pending instead of Bound.
May  5 13:18:06.913: INFO: PersistentVolumeClaim pvc-gvhgz found and phase=Bound (1m33.751788507s)
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  5 13:18:07.023: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-7h67m" in namespace "azurefile-6720" to be "Succeeded or Failed"
May  5 13:18:07.057: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 34.682743ms
May  5 13:18:09.094: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.071271116s
May  5 13:18:11.132: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10933613s
May  5 13:18:13.168: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.144993103s
May  5 13:18:15.205: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.182104815s
May  5 13:18:17.242: INFO: Pod "azurefile-volume-tester-7h67m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.219710598s
... skipping 8 lines ...