This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: add cloudConfigSecret in helm install
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-17 14:55
Elapsed34m34s
Revision24c9b8bf97117e0c6d70a0623521759f7977485d
Refs 943

No Test Failures!


Error lines from build-log.txt

... skipping 68 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.5.0-1cc160519e48762ab6e84d606284d643632cc5f5 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.5.0-1cc160519e48762ab6e84d606284d643632cc5f5 not found: manifest unknown: manifest tagged by "v1.5.0-1cc160519e48762ab6e84d606284d643632cc5f5" 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.5.0-1cc160519e48762ab6e84d606284d643632cc5f5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=1cc160519e48762ab6e84d606284d643632cc5f5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-07-17T15:01:18Z -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 1569 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 819 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
E0717 15:10:19.381871   13932 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0717 15:10:19.383970   13932 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0717 15:10:19.384482   13932 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0717 15:10:19.384628   13932 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0717 15:10:19.384728   13932 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0717 15:10:19.384815   13932 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0717 15:10:19.384883   13932 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 17 15:10:20.979: INFO: >>> kubeConfig: /root/tmp516000047/kubeconfig/kubeconfig.westus2.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0717 15:10:21.269248   13932 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
... skipping 2 lines ...

S [SKIPPING] [0.407 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
I0717 15:10:22.489805   13932 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-x4tjha5c/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume"

STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 17 15:10:26.476: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vnpml" in namespace "azuredisk-5541" to be "Succeeded or Failed"
Jul 17 15:10:26.535: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 58.702253ms
Jul 17 15:10:28.593: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116954941s
Jul 17 15:10:30.652: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 4.175481703s
Jul 17 15:10:32.710: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 6.234260935s
Jul 17 15:10:34.769: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 8.293311855s
Jul 17 15:10:36.827: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 10.351255525s
... skipping 9 lines ...
Jul 17 15:10:57.423: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 30.947277519s
Jul 17 15:10:59.484: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 33.007516376s
Jul 17 15:11:01.543: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 35.066716803s
Jul 17 15:11:03.600: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Pending", Reason="", readiness=false. Elapsed: 37.123897787s
Jul 17 15:11:05.659: INFO: Pod "azuredisk-volume-tester-vnpml": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.182451695s
STEP: Saw pod success
Jul 17 15:11:05.659: INFO: Pod "azuredisk-volume-tester-vnpml" satisfied condition "Succeeded or Failed"
Jul 17 15:11:05.659: INFO: deleting Pod "azuredisk-5541"/"azuredisk-volume-tester-vnpml"
Jul 17 15:11:05.747: INFO: Pod azuredisk-volume-tester-vnpml has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-vnpml in namespace azuredisk-5541
Jul 17 15:11:05.809: 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 17 15:11:07.520: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-97snq" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jul 17 15:11:07.577: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 56.701121ms
Jul 17 15:11:09.634: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.114089375s
Jul 17 15:11:11.692: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.172116327s
Jul 17 15:11:13.750: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.229585361s
Jul 17 15:11:15.809: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.28871099s
Jul 17 15:11:17.867: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.346625728s
... skipping 10 lines ...
Jul 17 15:11:40.513: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 32.993282062s
Jul 17 15:11:42.572: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 35.05177545s
Jul 17 15:11:44.630: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 37.10986328s
Jul 17 15:11:46.688: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Pending", Reason="", readiness=false. Elapsed: 39.167719531s
Jul 17 15:11:48.746: INFO: Pod "azuredisk-volume-tester-97snq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.22619574s
STEP: Saw pod success
Jul 17 15:11:48.746: INFO: Pod "azuredisk-volume-tester-97snq" satisfied condition "Succeeded or Failed"
Jul 17 15:11:48.746: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-97snq"
Jul 17 15:11:48.807: INFO: Pod azuredisk-volume-tester-97snq has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-97snq 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 17 15:12:56.062: INFO: deleting Pod "azuredisk-1957"/"azuredisk-volume-tester-p4nv6"
Jul 17 15:12:56.151: INFO: Error getting logs for pod azuredisk-volume-tester-p4nv6: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-p4nv6)
STEP: Deleting pod azuredisk-volume-tester-p4nv6 in namespace azuredisk-1957
STEP: validating provisioned PV
STEP: checking the PV
Jul 17 15:12:56.325: INFO: deleting PVC "azuredisk-1957"/"pvc-blxsp"
Jul 17 15:12:56.325: INFO: Deleting PersistentVolumeClaim "pvc-blxsp"
STEP: waiting for claim's PV "pvc-0111e8cc-8c7c-414d-884a-2d7aa218f972" to be deleted
... skipping 43 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 17 15:14:14.087: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2vpjl" in namespace "azuredisk-8705" to be "Succeeded or Failed"
Jul 17 15:14:14.144: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 56.971528ms
Jul 17 15:14:16.203: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.115757058s
Jul 17 15:14:18.262: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.175061004s
Jul 17 15:14:20.321: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.23437921s
Jul 17 15:14:22.381: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.293899888s
Jul 17 15:14:24.441: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.354354681s
... skipping 3 lines ...
Jul 17 15:14:32.710: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 18.623244843s
Jul 17 15:14:34.769: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 20.682543167s
Jul 17 15:14:36.828: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 22.740746932s
Jul 17 15:14:38.886: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Pending", Reason="", readiness=false. Elapsed: 24.798603514s
Jul 17 15:14:40.943: INFO: Pod "azuredisk-volume-tester-2vpjl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.856014601s
STEP: Saw pod success
Jul 17 15:14:40.943: INFO: Pod "azuredisk-volume-tester-2vpjl" satisfied condition "Succeeded or Failed"
Jul 17 15:14:40.943: INFO: deleting Pod "azuredisk-8705"/"azuredisk-volume-tester-2vpjl"
Jul 17 15:14:41.026: INFO: Pod azuredisk-volume-tester-2vpjl has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-2vpjl in namespace azuredisk-8705
STEP: validating provisioned PV
STEP: checking the PV
... skipping 9 lines ...