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-09 17:54
Elapsed32m44s
Revision1dc778fee1f07b72136a4698871c42714c4146dd
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   119k      0 --:--:-- --:--:-- --:--:--  119k
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-18deb8c55a3e4c8d389ee7c78ce71fb3f92fd904 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-18deb8c55a3e4c8d389ee7c78ce71fb3f92fd904 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-18deb8c55a3e4c8d389ee7c78ce71fb3f92fd904" 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-18deb8c55a3e4c8d389ee7c78ce71fb3f92fd904 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=18deb8c55a3e4c8d389ee7c78ce71fb3f92fd904 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-09T18:00:46Z -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 1656 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 253 lines ...
Go Version: go1.16.4
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0609 18:10:06.001681   14633 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
I0609 18:10:06.002893   14633 azuredisk_v2.go:173] disable UseInstanceMetadata for controller
I0609 18:10:06.003589   14633 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0609 18:10:06.003628   14633 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0609 18:10:06.003634   14633 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0609 18:10:06.003640   14633 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0609 18:10:06.003646   14633 driver.go:80] 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
Jun  9 18:10:07.681: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2dd2x" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jun  9 18:10:07.726: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 45.157747ms
Jun  9 18:10:09.778: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 2.097169964s
Jun  9 18:10:11.823: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 4.141924259s
Jun  9 18:10:13.869: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 6.188424063s
Jun  9 18:10:15.925: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 8.244131251s
Jun  9 18:10:17.972: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 10.290991748s
... skipping 16 lines ...
Jun  9 18:10:52.779: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 45.098402452s
Jun  9 18:10:54.826: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 47.144664699s
Jun  9 18:10:56.872: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 49.191063326s
Jun  9 18:10:58.920: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Pending", Reason="", readiness=false. Elapsed: 51.238739819s
Jun  9 18:11:00.968: INFO: Pod "azuredisk-volume-tester-2dd2x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 53.287061571s
STEP: Saw pod success
Jun  9 18:11:00.968: INFO: Pod "azuredisk-volume-tester-2dd2x" satisfied condition "Succeeded or Failed"
Jun  9 18:11:00.968: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-2dd2x"
Jun  9 18:11:01.071: INFO: Pod azuredisk-volume-tester-2dd2x has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-2dd2x 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  9 18:12:07.374: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-msxmn"
Jun  9 18:12:07.423: INFO: Error getting logs for pod azuredisk-volume-tester-msxmn: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-msxmn)
STEP: Deleting pod azuredisk-volume-tester-msxmn in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Jun  9 18:12:07.561: INFO: deleting PVC "azuredisk-1318"/"pvc-xv8z6"
Jun  9 18:12:07.561: INFO: Deleting PersistentVolumeClaim "pvc-xv8z6"
STEP: waiting for claim's PV "pvc-3c4bce74-e4d0-4f93-aa8f-53c84f47cd08" to be deleted
... skipping 7 lines ...