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:54
Elapsed35m17s
Revision24c9b8bf97117e0c6d70a0623521759f7977485d
Refs 943

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   215k      0 --:--:-- --:--:-- --:--:--  215k
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:00:40Z -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 1611 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 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
E0717 15:11:21.466496   14124 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0717 15:11:21.467498   14124 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0717 15:11:21.467792   14124 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0717 15:11:21.467816   14124 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0717 15:11:21.467823   14124 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0717 15:11:21.467830   14124 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0717 15:11:21.467835   14124 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 17 15:11:23.837: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lb4mh" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jul 17 15:11:23.892: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 54.394678ms
Jul 17 15:11:25.947: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.110103252s
Jul 17 15:11:28.003: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165721028s
Jul 17 15:11:30.062: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.224635715s
Jul 17 15:11:32.118: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.280509811s
Jul 17 15:11:34.174: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.336275444s
... skipping 6 lines ...
Jul 17 15:11:48.563: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 24.726091991s
Jul 17 15:11:50.620: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 26.782697236s
Jul 17 15:11:52.676: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 28.839188089s
Jul 17 15:11:54.732: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.89423782s
Jul 17 15:11:56.788: INFO: Pod "azuredisk-volume-tester-lb4mh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.950450586s
STEP: Saw pod success
Jul 17 15:11:56.788: INFO: Pod "azuredisk-volume-tester-lb4mh" satisfied condition "Succeeded or Failed"
Jul 17 15:11:56.788: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-lb4mh"
Jul 17 15:11:56.871: INFO: Pod azuredisk-volume-tester-lb4mh has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-lb4mh in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 46 lines ...
Jul 17 15:12:41.690: INFO: PersistentVolumeClaim pvc-j4k6g found but phase is Pending instead of Bound.
Jul 17 15:12:43.746: INFO: PersistentVolumeClaim pvc-j4k6g found and phase=Bound (4.163310972s)
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 17 15:12:43.915: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-76r8r" in namespace "azuredisk-1318" to be "Succeeded or Failed"
Jul 17 15:12:43.977: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 61.851374ms
Jul 17 15:12:46.040: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124459472s
Jul 17 15:12:48.096: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.180265081s
Jul 17 15:12:50.152: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.237119141s
Jul 17 15:12:52.208: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.29224506s
Jul 17 15:12:54.262: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.347100608s
Jul 17 15:12:56.319: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 12.403219738s
Jul 17 15:12:58.376: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 14.460654741s
Jul 17 15:13:00.432: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 16.51705757s
Jul 17 15:13:02.489: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 18.574022022s
Jul 17 15:13:04.546: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Pending", Reason="", readiness=false. Elapsed: 20.6308637s
Jul 17 15:13:06.605: INFO: Pod "azuredisk-volume-tester-76r8r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.689520151s
STEP: Saw pod success
Jul 17 15:13:06.605: INFO: Pod "azuredisk-volume-tester-76r8r" satisfied condition "Succeeded or Failed"
Jul 17 15:13:06.605: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-76r8r"
Jul 17 15:13:06.685: INFO: Pod azuredisk-volume-tester-76r8r has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-76r8r in namespace azuredisk-1318
Jul 17 15:13:06.746: INFO: deleting PVC "azuredisk-1318"/"pvc-j4k6g"
Jul 17 15:13:06.746: INFO: Deleting PersistentVolumeClaim "pvc-j4k6g"
... 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 17 15:13:49.097: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pnwx6" in namespace "azuredisk-694" to be "Succeeded or Failed"
Jul 17 15:13:49.152: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 55.689124ms
Jul 17 15:13:51.207: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.11066758s
Jul 17 15:13:53.264: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.166996143s
Jul 17 15:13:55.320: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.223283418s
Jul 17 15:13:57.378: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.280898258s
Jul 17 15:13:59.433: INFO: Pod "azuredisk-volume-tester-pnwx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.335979508s
... skipping 29 lines ...