This job view page is being replaced by Spyglass soon. Check out the new job view.
PRedreed: feat: Azure Disk CSI Driver V2 (a.k.a. Project Mandalay) initial implementation
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-06-07 21:55
Elapsed47m34s
Revisionb55ef0acf02481ab0d13b92d3b42c2dd60d2691a
Refs 864

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  91447      0 --:--:-- --:--:-- --:--:-- 91447
Downloading https://get.helm.sh/helm-v3.6.0-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:v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12" 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=v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=391fc957606472151f04be2916020c5ca7adbd12 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-07T22:02:30Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.topologyKey=topology.disk.csi.azure.com/zone -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.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 1286 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12" 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.schedulerVersion=v2.0.0-alpha.1-391fc957606472151f04be2916020c5ca7adbd12 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=391fc957606472151f04be2916020c5ca7adbd12 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-07T22:11:30Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -extldflags "-static"" -mod vendor -o _output/amd64/azdiskschedulerextender.exe ./pkg/azdiskschedulerextender
docker buildx rm container-builder || true
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
... skipping 1645 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 227 lines ...
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              Nil status indicates that the underlying volume of AzVolumeAttachment
              has not yet been attached to the specified node
            properties:
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 197 lines ...
            - volumeCapability
            type: object
          status:
            description: status represents the current state of AzVolume. Nil status
              indicates that the underlying volume has not yet been provisioned
            properties:
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 1006 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 252 lines ...
------------------------------
Dynamic Provisioning [multi-az] 
  should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [default-scheduler]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:105
STEP: Creating a kubernetes client
Jun  7 22:18:31.297: INFO: >>> kubeConfig: /root/tmp650411608/kubeconfig/kubeconfig.eastus2.json
E0607 22:18:31.300729   14529 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
STEP: Building a namespace api object, basename azuredisk
I0607 22:18:31.301481   14529 azuredisk_v2.go:173] disable UseInstanceMetadata for controller
I0607 22:18:31.301651   14529 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0607 22:18:31.301664   14529 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0607 22:18:31.301668   14529 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0607 22:18:31.301681   14529 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
... skipping 14 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
Jun  7 22:18:32.967: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fjt5c" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jun  7 22:18:33.015: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 48.155875ms
Jun  7 22:18:35.060: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.093553525s
Jun  7 22:18:37.106: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.139389215s
Jun  7 22:18:39.151: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.18486385s
Jun  7 22:18:41.198: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.231029066s
Jun  7 22:18:43.243: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.276728184s
... skipping 16 lines ...
Jun  7 22:19:18.041: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 45.07489123s
Jun  7 22:19:20.088: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 47.12155625s
Jun  7 22:19:22.141: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 49.174478651s
Jun  7 22:19:24.189: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Pending", Reason="", readiness=false. Elapsed: 51.222166029s
Jun  7 22:19:26.235: INFO: Pod "azuredisk-volume-tester-fjt5c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 53.26877004s
STEP: Saw pod success
Jun  7 22:19:26.235: INFO: Pod "azuredisk-volume-tester-fjt5c" satisfied condition "Succeeded or Failed"
Jun  7 22:19:26.235: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-fjt5c"
Jun  7 22:19:26.348: INFO: Pod azuredisk-volume-tester-fjt5c has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-fjt5c in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 41 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
Jun  7 22:20:32.593: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-4tk4g"
Jun  7 22:20:32.650: INFO: Error getting logs for pod azuredisk-volume-tester-4tk4g: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-4tk4g)
STEP: Deleting pod azuredisk-volume-tester-4tk4g in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Jun  7 22:20:32.787: INFO: deleting PVC "azuredisk-1318"/"pvc-l8rd4"
Jun  7 22:20:32.787: INFO: Deleting PersistentVolumeClaim "pvc-l8rd4"
STEP: waiting for claim's PV "pvc-aabb3570-628c-4619-be9d-e4a3275014c7" to be deleted
... skipping 38 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
Jun  7 22:21:24.872: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vbhs5" in namespace "azuredisk-694" to be "Succeeded or Failed"
Jun  7 22:21:24.916: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 44.77754ms
Jun  7 22:21:26.962: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.089934054s
Jun  7 22:21:29.009: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.136959572s
Jun  7 22:21:31.056: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184638152s
Jun  7 22:21:33.104: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.232247308s
Jun  7 22:21:35.151: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.278951827s
... skipping 2 lines ...
Jun  7 22:21:41.292: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 16.420550538s
Jun  7 22:21:43.338: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 18.466614972s
Jun  7 22:21:45.384: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 20.512470754s
Jun  7 22:21:47.431: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Pending", Reason="", readiness=false. Elapsed: 22.559646897s
Jun  7 22:21:49.478: INFO: Pod "azuredisk-volume-tester-vbhs5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.60593676s
STEP: Saw pod success
Jun  7 22:21:49.478: INFO: Pod "azuredisk-volume-tester-vbhs5" satisfied condition "Succeeded or Failed"
Jun  7 22:21:49.478: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-vbhs5"
Jun  7 22:21:49.525: INFO: Pod azuredisk-volume-tester-vbhs5 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-vbhs5 in namespace azuredisk-694
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
Jun  7 22:22:31.747: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-v8spj" in namespace "azuredisk-3274" to be "Error status code"
Jun  7 22:22:31.791: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 44.680468ms
Jun  7 22:22:33.838: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091068051s
Jun  7 22:22:35.884: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.137207124s
Jun  7 22:22:37.931: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184419325s
Jun  7 22:22:39.978: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.231081245s
Jun  7 22:22:42.024: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.276884333s
Jun  7 22:22:44.071: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.323820548s
Jun  7 22:22:46.117: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.370268209s
Jun  7 22:22:48.168: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.420967788s
Jun  7 22:22:50.216: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.468836747s
Jun  7 22:22:52.262: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.515406926s
Jun  7 22:22:54.310: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Pending", Reason="", readiness=false. Elapsed: 22.56275947s
Jun  7 22:22:56.357: INFO: Pod "azuredisk-volume-tester-v8spj": Phase="Failed", Reason="", readiness=false. Elapsed: 24.610587678s
STEP: Saw pod failure
Jun  7 22:22:56.357: INFO: Pod "azuredisk-volume-tester-v8spj" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jun  7 22:22:56.405: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-v8spj"
Jun  7 22:22:56.452: INFO: Pod azuredisk-volume-tester-v8spj has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-v8spj in namespace azuredisk-3274
STEP: validating provisioned PV
... skipping 129 lines ...