This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: support disabling CreateVolume in CSI migration
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-19 14:08
Elapsed36m35s
Revision52de17e1c63f56493e47dd6bb4273284b38e8402
Refs 944

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   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-178403f9ee73133fabf1c2048060ab45834c0b6a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a not found: manifest unknown: manifest tagged by "v1.5.0-178403f9ee73133fabf1c2048060ab45834c0b6a" 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-178403f9ee73133fabf1c2048060ab45834c0b6a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=178403f9ee73133fabf1c2048060ab45834c0b6a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-07-19T14:16:49Z -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 1536 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 175 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
E0719 14:24:41.508900   14080 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0719 14:24:41.509808   14080 azuredisk.go:211] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0719 14:24:41.510068   14080 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0719 14:24:41.510139   14080 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0719 14:24:41.510162   14080 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0719 14:24:41.510178   14080 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0719 14:24:41.510208   14080 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 19 14:24:42.833: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-4r5ph" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jul 19 14:24:42.868: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 35.504929ms
Jul 19 14:24:44.907: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073790324s
Jul 19 14:24:46.944: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 4.111017944s
Jul 19 14:24:48.981: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 6.14821659s
Jul 19 14:24:51.019: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 8.185591831s
Jul 19 14:24:53.056: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 10.223517104s
... skipping 3 lines ...
Jul 19 14:25:01.209: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 18.376521056s
Jul 19 14:25:03.247: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 20.414007634s
Jul 19 14:25:05.284: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 22.450919642s
Jul 19 14:25:07.322: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Pending", Reason="", readiness=false. Elapsed: 24.489101963s
Jul 19 14:25:09.363: INFO: Pod "azuredisk-volume-tester-4r5ph": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.530035485s
STEP: Saw pod success
Jul 19 14:25:09.363: INFO: Pod "azuredisk-volume-tester-4r5ph" satisfied condition "Succeeded or Failed"
Jul 19 14:25:09.363: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-4r5ph"
Jul 19 14:25:09.463: INFO: Pod azuredisk-volume-tester-4r5ph has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-4r5ph in namespace azuredisk-8081
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 19 14:26:17.386: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-hxr5p"
Jul 19 14:26:17.425: INFO: Error getting logs for pod azuredisk-volume-tester-hxr5p: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-hxr5p)
STEP: Deleting pod azuredisk-volume-tester-hxr5p in namespace azuredisk-3274
STEP: validating provisioned PV
STEP: checking the PV
Jul 19 14:26:17.536: INFO: deleting PVC "azuredisk-3274"/"pvc-47d7x"
Jul 19 14:26:17.536: INFO: Deleting PersistentVolumeClaim "pvc-47d7x"
STEP: waiting for claim's PV "pvc-a74a959f-8bba-480c-844a-87f3a934c913" 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 19 14:27:04.253: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-kq4nb" in namespace "azuredisk-495" to be "Succeeded or Failed"
Jul 19 14:27:04.289: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 35.718022ms
Jul 19 14:27:06.325: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.072227438s
Jul 19 14:27:08.362: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.108820915s
Jul 19 14:27:10.402: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.14930333s
Jul 19 14:27:12.440: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.187326256s
Jul 19 14:27:14.478: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.224768117s
... skipping 3 lines ...
Jul 19 14:27:22.627: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.374620235s
Jul 19 14:27:24.665: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.412174942s
Jul 19 14:27:26.702: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.449496125s
Jul 19 14:27:28.744: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Pending", Reason="", readiness=false. Elapsed: 24.491259182s
Jul 19 14:27:30.782: INFO: Pod "azuredisk-volume-tester-kq4nb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.529547531s
STEP: Saw pod success
Jul 19 14:27:30.782: INFO: Pod "azuredisk-volume-tester-kq4nb" satisfied condition "Succeeded or Failed"
Jul 19 14:27:30.782: INFO: deleting Pod "azuredisk-495"/"azuredisk-volume-tester-kq4nb"
Jul 19 14:27:30.822: INFO: Pod azuredisk-volume-tester-kq4nb has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-kq4nb in namespace azuredisk-495
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 19 14:28:12.628: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-vpfwh" in namespace "azuredisk-9947" to be "Error status code"
Jul 19 14:28:12.661: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 33.627451ms
Jul 19 14:28:14.697: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069086751s
Jul 19 14:28:16.732: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104205341s
Jul 19 14:28:18.768: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.139727289s
Jul 19 14:28:20.803: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175259711s
Jul 19 14:28:22.838: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209974936s
Jul 19 14:28:24.874: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.246079922s
Jul 19 14:28:26.909: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.280716882s
Jul 19 14:28:28.945: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.316801034s
Jul 19 14:28:30.980: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.351903839s
Jul 19 14:28:33.015: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 20.38693337s
Jul 19 14:28:35.049: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Pending", Reason="", readiness=false. Elapsed: 22.421251589s
Jul 19 14:28:37.085: INFO: Pod "azuredisk-volume-tester-vpfwh": Phase="Failed", Reason="", readiness=false. Elapsed: 24.456843867s
STEP: Saw pod failure
Jul 19 14:28:37.085: INFO: Pod "azuredisk-volume-tester-vpfwh" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 19 14:28:37.125: INFO: deleting Pod "azuredisk-9947"/"azuredisk-volume-tester-vpfwh"
Jul 19 14:28:37.162: INFO: Pod azuredisk-volume-tester-vpfwh has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-vpfwh in namespace azuredisk-9947
STEP: validating provisioned PV
... skipping 71 lines ...