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
Elapsed36m24s
Revisionec69880f5dd844ea39987b3e044521f90fe3d61e
Refs 947

No Test Failures!


Error lines from build-log.txt

... skipping 69 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   219k      0 --:--:-- --:--:-- --:--:--  219k
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:12:25Z -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 1496 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 174 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:19:58.232784   14125 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0726 23:19:58.234944   14125 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0726 23:19:58.235393   14125 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0726 23:19:58.235506   14125 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0726 23:19:58.235569   14125 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0726 23:19:58.235640   14125 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0726 23:19:58.235706   14125 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 65 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:263
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:158
STEP: Creating a kubernetes client
Jul 26 23:19:59.287: INFO: >>> kubeConfig: /root/tmp087156572/kubeconfig/kubeconfig.eastus2.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0726 23:19:59.471560   14125 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
... skipping 2 lines ...

S [SKIPPING] [0.258 seconds]
Pre-Provisioned
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:37
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:67
    should fail when maxShares is invalid [disk.csi.azure.com][windows] [It]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:158

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:263
------------------------------
... skipping 51 lines ...
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0726 23:20:00.238494   14125 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
STEP: Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-sf0k4exi/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume"

STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 26 23:20:03.997: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mkr98" in namespace "azuredisk-5541" to be "Succeeded or Failed"
Jul 26 23:20:04.033: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 35.49974ms
Jul 26 23:20:06.070: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072863387s
Jul 26 23:20:08.107: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110403412s
Jul 26 23:20:10.146: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 6.149120118s
Jul 26 23:20:12.186: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 8.1890788s
Jul 26 23:20:14.225: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 10.228153684s
Jul 26 23:20:16.262: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 12.264517547s
Jul 26 23:20:18.299: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 14.302142854s
Jul 26 23:20:20.338: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 16.340540699s
Jul 26 23:20:22.376: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 18.378491651s
Jul 26 23:20:24.413: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Pending", Reason="", readiness=false. Elapsed: 20.415840911s
Jul 26 23:20:26.450: INFO: Pod "azuredisk-volume-tester-mkr98": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.453326939s
STEP: Saw pod success
Jul 26 23:20:26.450: INFO: Pod "azuredisk-volume-tester-mkr98" satisfied condition "Succeeded or Failed"
Jul 26 23:20:26.450: INFO: deleting Pod "azuredisk-5541"/"azuredisk-volume-tester-mkr98"
Jul 26 23:20:26.546: INFO: Pod azuredisk-volume-tester-mkr98 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-mkr98 in namespace azuredisk-5541
Jul 26 23:20:26.585: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-5541" for this suite.
... skipping 21 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:20:27.804: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pcv8g" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jul 26 23:20:27.840: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 36.209118ms
Jul 26 23:20:29.879: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.074409245s
Jul 26 23:20:31.915: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.111079119s
Jul 26 23:20:33.953: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.14909414s
Jul 26 23:20:35.991: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.186995723s
Jul 26 23:20:38.030: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.226258807s
... skipping 2 lines ...
Jul 26 23:20:44.147: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 16.342805725s
Jul 26 23:20:46.186: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 18.381618917s
Jul 26 23:20:48.224: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 20.41983055s
Jul 26 23:20:50.263: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Pending", Reason="", readiness=false. Elapsed: 22.459028565s
Jul 26 23:20:52.304: INFO: Pod "azuredisk-volume-tester-pcv8g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.499329206s
STEP: Saw pod success
Jul 26 23:20:52.304: INFO: Pod "azuredisk-volume-tester-pcv8g" satisfied condition "Succeeded or Failed"
Jul 26 23:20:52.304: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-pcv8g"
Jul 26 23:20:52.347: INFO: Pod azuredisk-volume-tester-pcv8g has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-pcv8g in namespace azuredisk-5356
STEP: validating provisioned PV
STEP: checking the PV
... skipping 95 lines ...
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 has 'FailedMount' event
Jul 26 23:21:59.580: INFO: deleting Pod "azuredisk-1957"/"azuredisk-volume-tester-mdzdj"
Jul 26 23:21:59.618: INFO: Error getting logs for pod azuredisk-volume-tester-mdzdj: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-mdzdj)
STEP: Deleting pod azuredisk-volume-tester-mdzdj in namespace azuredisk-1957
STEP: validating provisioned PV
STEP: checking the PV
Jul 26 23:21:59.731: INFO: deleting PVC "azuredisk-1957"/"pvc-jqgb9"
Jul 26 23:21:59.731: INFO: Deleting PersistentVolumeClaim "pvc-jqgb9"
STEP: waiting for claim's PV "pvc-b2fa6ff9-bd91-457a-b68a-b7541e5d245b" to be deleted
... skipping 37 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:22:47.391: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ld8l6" in namespace "azuredisk-8705" to be "Succeeded or Failed"
Jul 26 23:22:47.429: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 37.360225ms
Jul 26 23:22:49.467: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075611321s
Jul 26 23:22:51.506: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114660459s
Jul 26 23:22:53.544: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.153183419s
Jul 26 23:22:55.584: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.192735684s
Jul 26 23:22:57.622: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.230803464s
... skipping 2 lines ...
Jul 26 23:23:03.741: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.349940664s
Jul 26 23:23:05.779: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.387330893s
Jul 26 23:23:07.821: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 20.429986464s
Jul 26 23:23:09.856: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Pending", Reason="", readiness=false. Elapsed: 22.464545568s
Jul 26 23:23:11.891: INFO: Pod "azuredisk-volume-tester-ld8l6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.499835443s
STEP: Saw pod success
Jul 26 23:23:11.891: INFO: Pod "azuredisk-volume-tester-ld8l6" satisfied condition "Succeeded or Failed"
Jul 26 23:23:11.891: INFO: deleting Pod "azuredisk-8705"/"azuredisk-volume-tester-ld8l6"
Jul 26 23:23:11.929: INFO: Pod azuredisk-volume-tester-ld8l6 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-ld8l6 in namespace azuredisk-8705
STEP: validating provisioned PV
STEP: checking the PV
... 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 an error
Jul 26 23:23:54.055: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-kbsbc" in namespace "azuredisk-2451" to be "Error status code"
Jul 26 23:23:54.087: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 32.433689ms
Jul 26 23:23:56.124: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069134299s
Jul 26 23:23:58.159: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104356848s
Jul 26 23:24:00.193: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138705616s
Jul 26 23:24:02.228: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173215635s
Jul 26 23:24:04.263: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208152556s
Jul 26 23:24:06.299: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 12.244335012s
Jul 26 23:24:08.334: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 14.278991643s
Jul 26 23:24:10.369: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 16.314123623s
Jul 26 23:24:12.403: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 18.348550965s
Jul 26 23:24:14.453: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 20.398679455s
Jul 26 23:24:16.488: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Pending", Reason="", readiness=false. Elapsed: 22.433601368s
Jul 26 23:24:18.522: INFO: Pod "azuredisk-volume-tester-kbsbc": Phase="Failed", Reason="", readiness=false. Elapsed: 24.46769731s
STEP: Saw pod failure
Jul 26 23:24:18.522: INFO: Pod "azuredisk-volume-tester-kbsbc" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 26 23:24:18.560: INFO: deleting Pod "azuredisk-2451"/"azuredisk-volume-tester-kbsbc"
Jul 26 23:24:18.597: INFO: Pod azuredisk-volume-tester-kbsbc has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-kbsbc in namespace azuredisk-2451
STEP: validating provisioned PV
... skipping 80 lines ...