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-14 16:39
Elapsed37m35s
Revision7786ef081b4ade4f976617cfd0fabdddcc0bb504
Refs 864

No Test Failures!


Error lines from build-log.txt

... skipping 70 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   192k      0 --:--:-- --:--:-- --:--:--  192k
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-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e" 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-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-14T16:43:59Z -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 1265 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-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:v2.0.0-alpha.1-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e" 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-7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=7b6aa8b2f890981fc2b8aa3a70b00342ef37aa5e -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-14T16:50:13Z -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 1631 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
E0614 16:56:12.179919   14598 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
I0614 16:56:12.180754   14598 azuredisk_v2.go:173] disable UseInstanceMetadata for controller
I0614 16:56:12.181041   14598 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0614 16:56:12.181061   14598 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0614 16:56:12.181065   14598 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0614 16:56:12.181071   14598 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0614 16:56:12.181075   14598 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 14 16:56:13.499: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9xrtb" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jun 14 16:56:13.532: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 32.973448ms
Jun 14 16:56:15.567: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068667832s
Jun 14 16:56:17.603: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103926666s
Jun 14 16:56:19.638: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138944639s
Jun 14 16:56:21.672: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173876113s
Jun 14 16:56:23.708: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.209228007s
... skipping 16 lines ...
Jun 14 16:56:58.313: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 44.814050711s
Jun 14 16:57:00.349: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 46.850395499s
Jun 14 16:57:02.383: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 48.884463875s
Jun 14 16:57:04.417: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Pending", Reason="", readiness=false. Elapsed: 50.918699732s
Jun 14 16:57:06.454: INFO: Pod "azuredisk-volume-tester-9xrtb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 52.955759519s
STEP: Saw pod success
Jun 14 16:57:06.454: INFO: Pod "azuredisk-volume-tester-9xrtb" satisfied condition "Succeeded or Failed"
Jun 14 16:57:06.454: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-9xrtb"
Jun 14 16:57:06.545: INFO: Pod azuredisk-volume-tester-9xrtb has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-9xrtb 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 14 16:58:12.357: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-zs9df"
Jun 14 16:58:12.392: INFO: Error getting logs for pod azuredisk-volume-tester-zs9df: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-zs9df)
STEP: Deleting pod azuredisk-volume-tester-zs9df in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Jun 14 16:58:12.496: INFO: deleting PVC "azuredisk-1318"/"pvc-8vwsz"
Jun 14 16:58:12.496: INFO: Deleting PersistentVolumeClaim "pvc-8vwsz"
STEP: waiting for claim's PV "pvc-1562fd0b-3ce1-47b5-9b86-c9998367d5a6" 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
Jun 14 16:58:59.088: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hv9bk" in namespace "azuredisk-694" to be "Succeeded or Failed"
Jun 14 16:58:59.121: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 33.310968ms
Jun 14 16:59:01.156: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067863224s
Jun 14 16:59:03.192: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103911909s
Jun 14 16:59:05.226: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137791244s
Jun 14 16:59:07.262: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173758269s
Jun 14 16:59:09.297: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208958843s
... skipping 2 lines ...
Jun 14 16:59:15.402: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.313890233s
Jun 14 16:59:17.437: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.349581569s
Jun 14 16:59:19.472: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.383839776s
Jun 14 16:59:21.506: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Pending", Reason="", readiness=false. Elapsed: 22.418180342s
Jun 14 16:59:23.542: INFO: Pod "azuredisk-volume-tester-hv9bk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.453871929s
STEP: Saw pod success
Jun 14 16:59:23.542: INFO: Pod "azuredisk-volume-tester-hv9bk" satisfied condition "Succeeded or Failed"
Jun 14 16:59:23.542: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-hv9bk"
Jun 14 16:59:23.578: INFO: Pod azuredisk-volume-tester-hv9bk has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-hv9bk 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 14 17:00:05.230: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-zvkf4" in namespace "azuredisk-3274" to be "Error status code"
Jun 14 17:00:05.263: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 33.014168ms
Jun 14 17:00:07.298: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067326777s
Jun 14 17:00:09.335: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.104544565s
Jun 14 17:00:11.369: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138968123s
Jun 14 17:00:13.406: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.175248601s
Jun 14 17:00:15.441: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.21022364s
Jun 14 17:00:17.475: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.24440035s
Jun 14 17:00:19.509: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.278593127s
Jun 14 17:00:21.544: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.313906656s
Jun 14 17:00:23.579: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.348413545s
Jun 14 17:00:25.614: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.383617324s
Jun 14 17:00:27.649: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Pending", Reason="", readiness=false. Elapsed: 22.418998766s
Jun 14 17:00:29.685: INFO: Pod "azuredisk-volume-tester-zvkf4": Phase="Failed", Reason="", readiness=false. Elapsed: 24.454647055s
STEP: Saw pod failure
Jun 14 17:00:29.685: INFO: Pod "azuredisk-volume-tester-zvkf4" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jun 14 17:00:29.721: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-zvkf4"
Jun 14 17:00:29.766: INFO: Pod azuredisk-volume-tester-zvkf4 has the following logs: touch: /mnt/test-1/data: Read-only file system

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