This job view page is being replaced by Spyglass soon. Check out the new job view.
PRlandreasyan: [V2] Adding options to configure attach/detach rate limiter on azure client
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-09-17 02:56
Elapsed38m19s
Revisioned9a897eee7ef46455243232ca9ea9f6d12f8cc6
Refs 1515

No Test Failures!


Error lines from build-log.txt

... skipping 101 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   167k      0 --:--:-- --:--:-- --:--:--  167k
Downloading https://get.helm.sh/helm-v3.9.4-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/azuredisk-csi:latest-v2-86de843aafe678afb0dfcc6e7bf35856b9cc28aa || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-86de843aafe678afb0dfcc6e7bf35856b9cc28aa not found: manifest unknown: manifest tagged by "latest-v2-86de843aafe678afb0dfcc6e7bf35856b9cc28aa" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-86de843aafe678afb0dfcc6e7bf35856b9cc28aa -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=86de843aafe678afb0dfcc6e7bf35856b9cc28aa -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-09-17T03:04:02Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 1764 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status Required
            properties:
              detail:
                description: Status summarizes the current attachment state of the
                  volume attachment Nil Status indicates that the volume has not yet
                  been attached to the node
                properties:
... skipping 7 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 90 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 13 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 169 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              detail:
                description: Current status detail of the AzVolume Nil detail indicates
                  that the volume has not been created
                properties:
                  accessible_topology:
... skipping 28 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 154 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 34 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 773 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - "--leader-election-namespace=kube-system"
            - '-handle-volume-inuse-error=false'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 244 lines ...
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
I0917 03:13:21.133360   15320 resource_setup.go:63] adding PV (pvc-b6691d33-606f-48da-94ce-6e0586f4d8f9) to pod ()
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep 17 03:13:21.193: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6xcgb" in namespace "azuredisk-9045" to be "Succeeded or Failed"
Sep 17 03:13:21.250: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 57.056608ms
Sep 17 03:13:23.308: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115094507s
Sep 17 03:13:25.367: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.173956371s
Sep 17 03:13:27.425: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.231950986s
Sep 17 03:13:29.483: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.289560935s
Sep 17 03:13:31.542: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.348567796s
... skipping 24 lines ...
Sep 17 03:14:23.004: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Running", Reason="", readiness=true. Elapsed: 1m1.810397733s
Sep 17 03:14:25.062: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Running", Reason="", readiness=true. Elapsed: 1m3.8683907s
Sep 17 03:14:27.120: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Running", Reason="", readiness=false. Elapsed: 1m5.926579923s
Sep 17 03:14:29.178: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Running", Reason="", readiness=false. Elapsed: 1m7.985081414s
Sep 17 03:14:31.238: INFO: Pod "azuredisk-volume-tester-6xcgb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m10.044449093s
STEP: Saw pod success
Sep 17 03:14:31.238: INFO: Pod "azuredisk-volume-tester-6xcgb" satisfied condition "Succeeded or Failed"
Sep 17 03:14:31.238: INFO: deleting Pod "azuredisk-9045"/"azuredisk-volume-tester-6xcgb"
Sep 17 03:14:31.335: INFO: Pod azuredisk-volume-tester-6xcgb has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-6xcgb in namespace azuredisk-9045
Sep 17 03:14:31.398: INFO: deleting PVC "azuredisk-9045"/"pvc-v8h46"
Sep 17 03:14:31.398: INFO: Deleting PersistentVolumeClaim "pvc-v8h46"
... skipping 46 lines ...
Sep 17 03:15:15.604: INFO: PersistentVolumeClaim pvc-bhncv found but phase is Pending instead of Bound.
Sep 17 03:15:17.662: INFO: PersistentVolumeClaim pvc-bhncv found and phase=Bound (4.172366416s)
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
Sep 17 03:15:17.843: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pgzdn" in namespace "azuredisk-9201" to be "Succeeded or Failed"
Sep 17 03:15:17.901: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 57.943745ms
Sep 17 03:15:19.959: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116853991s
Sep 17 03:15:22.018: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.175069016s
Sep 17 03:15:24.076: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.233800453s
Sep 17 03:15:26.136: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.293130056s
Sep 17 03:15:28.194: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.351424819s
... skipping 25 lines ...
Sep 17 03:16:21.716: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Running", Reason="", readiness=true. Elapsed: 1m3.873536059s
Sep 17 03:16:23.775: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Running", Reason="", readiness=true. Elapsed: 1m5.932342034s
Sep 17 03:16:25.834: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Running", Reason="", readiness=false. Elapsed: 1m7.991400722s
Sep 17 03:16:27.892: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.049399319s
Sep 17 03:16:29.951: INFO: Pod "azuredisk-volume-tester-pgzdn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m12.108005222s
STEP: Saw pod success
Sep 17 03:16:29.951: INFO: Pod "azuredisk-volume-tester-pgzdn" satisfied condition "Succeeded or Failed"
Sep 17 03:16:29.951: INFO: deleting Pod "azuredisk-9201"/"azuredisk-volume-tester-pgzdn"
Sep 17 03:16:30.055: INFO: Pod azuredisk-volume-tester-pgzdn has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-pgzdn in namespace azuredisk-9201
Sep 17 03:16:30.122: INFO: deleting PVC "azuredisk-9201"/"pvc-bhncv"
Sep 17 03:16:30.122: INFO: Deleting PersistentVolumeClaim "pvc-bhncv"
... skipping 39 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep 17 03:17:12.275: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z5b8q" in namespace "azuredisk-2454" to be "Succeeded or Failed"
Sep 17 03:17:12.332: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 57.400904ms
Sep 17 03:17:14.391: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115756846s
Sep 17 03:17:16.453: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.177791006s
Sep 17 03:17:18.511: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.235888601s
Sep 17 03:17:20.569: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.294439404s
Sep 17 03:17:22.628: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.353030443s
... skipping 16 lines ...
Sep 17 03:17:57.622: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Running", Reason="", readiness=true. Elapsed: 45.347086854s
Sep 17 03:17:59.682: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Running", Reason="", readiness=true. Elapsed: 47.406840338s
Sep 17 03:18:01.741: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Running", Reason="", readiness=false. Elapsed: 49.465968345s
Sep 17 03:18:03.800: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Running", Reason="", readiness=false. Elapsed: 51.524830977s
Sep 17 03:18:05.858: INFO: Pod "azuredisk-volume-tester-z5b8q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 53.582766464s
STEP: Saw pod success
Sep 17 03:18:05.858: INFO: Pod "azuredisk-volume-tester-z5b8q" satisfied condition "Succeeded or Failed"
Sep 17 03:18:05.858: INFO: deleting Pod "azuredisk-2454"/"azuredisk-volume-tester-z5b8q"
Sep 17 03:18:05.951: INFO: Pod azuredisk-volume-tester-z5b8q has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-z5b8q in namespace azuredisk-2454
STEP: validating provisioned PV
STEP: checking the PV
... skipping 47 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Sep 17 03:19:18.641: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9rt6q" in namespace "azuredisk-1485" to be "Succeeded or Failed"
Sep 17 03:19:18.724: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 83.017657ms
Sep 17 03:19:20.783: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.141172761s
Sep 17 03:19:22.841: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.199290308s
Sep 17 03:19:24.899: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 6.258036823s
Sep 17 03:19:26.957: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 8.315917999s
Sep 17 03:19:29.016: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 10.374371511s
Sep 17 03:19:31.075: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 12.433135509s
Sep 17 03:19:33.134: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 14.492440601s
Sep 17 03:19:35.194: INFO: Pod "azuredisk-volume-tester-9rt6q": Phase="Pending", Reason="", readiness=false. Elapsed: 16.552596568s
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-09-17T03:19:35Z"}
++ early_exit_handler
++ '[' -n 169 ']'
++ kill -TERM 169
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...