This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnearora-msft: fix: Update K8s version to fix snapshot e2e test
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-26 23:05
Elapsed36m21s
Revisionec69880f5dd844ea39987b3e044521f90fe3d61e
Refs 947

No Test Failures!


Error lines from build-log.txt

... skipping 72 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   211k      0 --:--:-- --:--:-- --:--:--  211k
Downloading https://get.helm.sh/helm-v3.6.3-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:v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a not found: manifest unknown: manifest tagged by "v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a" 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=v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=ebd1ba6092966acc91a5ad2057229a66dbea8b4a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-07-26T23:16:29Z -extldflags "-static""  -mod vendor -o _output/amd64/azurediskplugin.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 1556 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 841 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=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
... skipping 176 lines ...
Go Version: go1.16.6
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0726 23:24:02.563740   14088 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0726 23:24:02.564472   14088 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0726 23:24:02.564739   14088 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0726 23:24:02.564753   14088 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0726 23:24:02.564763   14088 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0726 23:24:02.564767   14088 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0726 23:24:02.564781   14088 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 13 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
Jul 26 23:24:04.543: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pxv4v" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jul 26 23:24:04.600: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 56.802489ms
Jul 26 23:24:06.657: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.114434783s
Jul 26 23:24:08.716: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.172677732s
Jul 26 23:24:10.775: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.232139663s
Jul 26 23:24:12.834: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.291167793s
Jul 26 23:24:14.892: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.349198299s
... skipping 6 lines ...
Jul 26 23:24:29.310: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 24.767086671s
Jul 26 23:24:31.368: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 26.825298206s
Jul 26 23:24:33.427: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 28.884364834s
Jul 26 23:24:35.486: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Pending", Reason="", readiness=false. Elapsed: 30.942910361s
Jul 26 23:24:37.545: INFO: Pod "azuredisk-volume-tester-pxv4v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 33.001944204s
STEP: Saw pod success
Jul 26 23:24:37.545: INFO: Pod "azuredisk-volume-tester-pxv4v" satisfied condition "Succeeded or Failed"
Jul 26 23:24:37.545: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-pxv4v"
Jul 26 23:24:37.634: INFO: Pod azuredisk-volume-tester-pxv4v has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-pxv4v in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 46 lines ...
Jul 26 23:25:22.330: INFO: PersistentVolumeClaim pvc-6f496 found but phase is Pending instead of Bound.
Jul 26 23:25:24.388: INFO: PersistentVolumeClaim pvc-6f496 found and phase=Bound (4.172773813s)
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 26 23:25:24.564: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hb8v4" in namespace "azuredisk-1318" to be "Succeeded or Failed"
Jul 26 23:25:24.621: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 56.824118ms
Jul 26 23:25:26.679: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115539257s
Jul 26 23:25:28.738: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.174714932s
Jul 26 23:25:30.797: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.232986893s
Jul 26 23:25:32.854: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.290380163s
Jul 26 23:25:34.914: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.350533504s
Jul 26 23:25:36.972: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.408335746s
Jul 26 23:25:39.031: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.467293933s
Jul 26 23:25:41.089: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.525452085s
Jul 26 23:25:43.148: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.584497222s
Jul 26 23:25:45.206: INFO: Pod "azuredisk-volume-tester-hb8v4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.642391209s
STEP: Saw pod success
Jul 26 23:25:45.206: INFO: Pod "azuredisk-volume-tester-hb8v4" satisfied condition "Succeeded or Failed"
Jul 26 23:25:45.206: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-hb8v4"
Jul 26 23:25:45.278: INFO: Pod azuredisk-volume-tester-hb8v4 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-hb8v4 in namespace azuredisk-1318
Jul 26 23:25:45.346: INFO: deleting PVC "azuredisk-1318"/"pvc-6f496"
Jul 26 23:25:45.347: INFO: Deleting PersistentVolumeClaim "pvc-6f496"
... skipping 41 lines ...