This job view page is being replaced by Spyglass soon. Check out the new job view.
PRedreed: [V2] build: disable provenance attestation to work around docker issue
ResultABORTED
Tests 0 failed / 0 succeeded
Started2023-02-02 00:34
Elapsed55m56s
Revisionfed380e17e859876de9b04df4872228ffc5570f5
Refs 1712

No Test Failures!


Error lines from build-log.txt

... skipping 805 lines ...
certificate.cert-manager.io "selfsigned-cert" deleted
# Create secret for AzureClusterIdentity
./hack/create-identity-secret.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Error from server (NotFound): secrets "cluster-identity-secret" not found
secret/cluster-identity-secret created
secret/cluster-identity-secret labeled
# Create customized cloud provider configs
./hack/create-custom-cloud-provider-config.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
... skipping 228 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11345  100 11345    0     0  79335      0 --:--:-- --:--:-- --:--:-- 79335
Downloading https://get.helm.sh/helm-v3.11.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 capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 not found: manifest unknown: manifest tagged by "latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3" 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=latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-02T00:55:28Z -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 242 lines ...

#9 exporting to image
#9 pushing layers 2.0s done
#9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:8bc0997ed9ad093d53071c30ccbcbb61d1ae0a5f6a54780d014894935f9998ec
#9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:8bc0997ed9ad093d53071c30ccbcbb61d1ae0a5f6a54780d014894935f9998ec 0.4s done
#9 DONE 6.4s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-02T00:59:09Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/arm64/azurediskpluginv2 ./pkg/azurediskplugin
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build . \
... skipping 112 lines ...
#8 exporting config sha256:5cec3e54c66c51e5fb11f7e8aba02404e58464590346081b0211d5e43b543b43 0.0s done
#8 pushing layers
#8 pushing layers 2.0s done
#8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:a548d1c28a8a02cfee6778e9f572400f3867ac6ef5a0700aa4564d859bc53737
#8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:a548d1c28a8a02cfee6778e9f572400f3867ac6ef5a0700aa4564d859bc53737 0.5s done
#8 DONE 6.1s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
for osversion in 1809 20H2 ltsc2022; do \
	OSVERSION=${osversion} make container-windows; \
done
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build . \
... skipping 66 lines ...
#10 exporting config sha256:d1648854e550bea463923f63f7007d886248f377ce409aa4f3fbbbd51bc81828 0.0s done
#10 pushing layers
#10 pushing layers 1.7s done
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-1809-amd64@sha256:1754aced8ebe1b64582e7e65268591c4cadd17746883f3b5804ffdc9155a3fa4
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-1809-amd64@sha256:1754aced8ebe1b64582e7e65268591c4cadd17746883f3b5804ffdc9155a3fa4 0.5s done
#10 DONE 6.0s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build . \
	--pull \
	--output=type=registry \
	--platform="windows/amd64" \
... skipping 72 lines ...
#10 exporting config sha256:c63d9058cbd32df1ac03ba04553b7811b141671ebe40118d703cf25c4f3af909 0.0s done
#10 pushing layers
#10 pushing layers 1.7s done
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-20H2-amd64@sha256:95c0515584727c7ae9e52bb6b522eba01e2fb77360b4b905b41fa7fd580f0800
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-20H2-amd64@sha256:95c0515584727c7ae9e52bb6b522eba01e2fb77360b4b905b41fa7fd580f0800 0.4s done
#10 DONE 6.1s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build . \
	--pull \
	--output=type=registry \
	--platform="windows/amd64" \
... skipping 71 lines ...
#10 exporting config sha256:e0aea80fed12458547d4b2bbf246e1e8a21515325d6a8761a25eb88484fe5c6b 0.0s done
#10 pushing layers
#10 pushing layers 1.8s done
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-ltsc2022-amd64@sha256:8999a529cc9155a230806fc1cc1468178c1e2950afc48fd2d66160d362238262
#10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-ltsc2022-amd64@sha256:8999a529cc9155a230806fc1cc1468178c1e2950afc48fd2d66160d362238262 0.4s done
#10 DONE 5.9s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker manifest create --amend capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3  capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64  capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64  capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-1809-amd64  capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-20H2-amd64  capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-ltsc2022-amd64
Created manifest list capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3
# add "os.version" field to windows images (based on https://github.com/kubernetes/kubernetes/blob/master/build/pause/Makefile)
set -x; \
for arch in amd64; do \
... skipping 74 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 not found: manifest unknown: manifest tagged by "latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx rm container-builder || true
container-builder removed
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
... skipping 153 lines ...

#8 exporting to image
#8 pushing layers 2.0s done
#8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:0cbc3022640822f53481fe3e513d2463e77d58785d12ba9b0ea1b578abf3bdc5
#8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:0cbc3022640822f53481fe3e513d2463e77d58785d12ba9b0ea1b578abf3bdc5 0.5s done
#8 DONE 5.2s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.schedulerVersion=latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-02T01:03:26Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName= -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/arm64/azdiskschedulerextender ./pkg/azdiskschedulerextender
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build . \
... skipping 38 lines ...
#7 exporting config sha256:c67b7d0c374f16f8f12010b63f9b9851aedd612af0e870650370983912467721 0.0s done
#7 pushing layers
#7 pushing layers 1.9s done
#7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:8fcb3c0822f2fe87867073989fac06d3aff675e673270da39b29771e5d5e397d
#7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:8fcb3c0822f2fe87867073989fac06d3aff675e673270da39b29771e5d5e397d 0.5s done
#7 DONE 4.9s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker manifest create --amend capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3  capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64  capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64
Created manifest list capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3
docker manifest push --purge capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3
sha256:8ee7ab726bfd7db3df32507cda5b2e3f70daca7ab7f1f10e930d89c9cc44de30
docker manifest inspect capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3
... skipping 880 lines ...
                    type: string
                type: object
                oneOf:
                - required: ["persistentVolumeClaimName"]
                - required: ["volumeSnapshotContentName"]
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 60 lines ...
                    type: string
                  volumeSnapshotContentName:
                    description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable.
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 254 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 108 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 359 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status Required
            properties:
              detail:
                description: Status summarizes the current attachment state of the
                  volume attachment Nil Status indicates that the volume has not yet
                  been attached to the node
                properties:
... skipping 7 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 90 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 13 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 169 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              detail:
                description: Current status detail of the AzVolume Nil detail indicates
                  that the volume has not been created
                properties:
                  accessible_topology:
... skipping 28 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 154 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 34 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 831 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - "--leader-election-namespace=kube-system"
            - '-handle-volume-inuse-error=false'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 325 lines ...
Feb  2 01:05:55.281: INFO: PersistentVolumeClaim pvc-dbv4m found but phase is Pending instead of Bound.
Feb  2 01:05:57.314: INFO: PersistentVolumeClaim pvc-dbv4m found and phase=Bound (2.066833566s)
STEP: checking the PVC 02/02/23 01:05:57.314
STEP: validating provisioned PV 02/02/23 01:05:57.346
STEP: checking the PV 02/02/23 01:05:57.378
STEP: deploying the pod 02/02/23 01:05:57.378
STEP: checking that the pod's command exits with an error 02/02/23 01:05:57.414
Feb  2 01:05:57.414: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-4m7q9" in namespace "azuredisk-6588" to be "Error status code"
Feb  2 01:05:57.447: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.609152ms
Feb  2 01:05:59.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067327711s
Feb  2 01:06:01.480: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066632035s
Feb  2 01:06:03.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066936909s
Feb  2 01:06:05.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.06789981s
Feb  2 01:06:07.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067471917s
... skipping 94 lines ...
Feb  2 01:09:17.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m20.068176135s
Feb  2 01:09:19.483: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m22.068712705s
Feb  2 01:09:21.485: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m24.070817925s
Feb  2 01:09:23.484: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.07010687s
Feb  2 01:09:25.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.068515591s
Feb  2 01:09:27.483: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.068797301s
Feb  2 01:09:29.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Failed", Reason="", readiness=false. Elapsed: 3m32.068457244s
STEP: Saw pod failure 02/02/23 01:09:29.482
Feb  2 01:09:29.482: INFO: Pod "azuredisk-volume-tester-4m7q9" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message 02/02/23 01:09:29.482
Feb  2 01:09:29.547: INFO: deleting Pod "azuredisk-6588"/"azuredisk-volume-tester-4m7q9"
Feb  2 01:09:29.581: INFO: Pod azuredisk-volume-tester-4m7q9 has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied.
At line:1 char:22
+ ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ...
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 54 lines ...
    Feb  2 01:05:55.281: INFO: PersistentVolumeClaim pvc-dbv4m found but phase is Pending instead of Bound.
    Feb  2 01:05:57.314: INFO: PersistentVolumeClaim pvc-dbv4m found and phase=Bound (2.066833566s)
    STEP: checking the PVC 02/02/23 01:05:57.314
    STEP: validating provisioned PV 02/02/23 01:05:57.346
    STEP: checking the PV 02/02/23 01:05:57.378
    STEP: deploying the pod 02/02/23 01:05:57.378
    STEP: checking that the pod's command exits with an error 02/02/23 01:05:57.414
    Feb  2 01:05:57.414: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-4m7q9" in namespace "azuredisk-6588" to be "Error status code"
    Feb  2 01:05:57.447: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 33.609152ms
    Feb  2 01:05:59.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067327711s
    Feb  2 01:06:01.480: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066632035s
    Feb  2 01:06:03.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066936909s
    Feb  2 01:06:05.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.06789981s
    Feb  2 01:06:07.481: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067471917s
... skipping 94 lines ...
    Feb  2 01:09:17.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m20.068176135s
    Feb  2 01:09:19.483: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m22.068712705s
    Feb  2 01:09:21.485: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=true. Elapsed: 3m24.070817925s
    Feb  2 01:09:23.484: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.07010687s
    Feb  2 01:09:25.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.068515591s
    Feb  2 01:09:27.483: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.068797301s
    Feb  2 01:09:29.482: INFO: Pod "azuredisk-volume-tester-4m7q9": Phase="Failed", Reason="", readiness=false. Elapsed: 3m32.068457244s
    STEP: Saw pod failure 02/02/23 01:09:29.482
    Feb  2 01:09:29.482: INFO: Pod "azuredisk-volume-tester-4m7q9" satisfied condition "Error status code"
    STEP: checking that pod logs contain expected message 02/02/23 01:09:29.482
    Feb  2 01:09:29.547: INFO: deleting Pod "azuredisk-6588"/"azuredisk-volume-tester-4m7q9"
    Feb  2 01:09:29.581: INFO: Pod azuredisk-volume-tester-4m7q9 has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied.
    At line:1 char:22
    + ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ...
    +                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 83 lines ...
Feb  2 01:10:27.446: INFO: PersistentVolumeClaim pvc-sgwd4 found and phase=Bound (2.067192522s)
STEP: checking the PVC 02/02/23 01:10:27.446
STEP: validating provisioned PV 02/02/23 01:10:27.478
STEP: checking the PV 02/02/23 01:10:27.51
STEP: attaching disk to node#0 02/02/23 01:10:27.554
STEP: deploying the pod 02/02/23 01:10:34.835
STEP: checking that the pod's command exits with no error 02/02/23 01:10:34.882
Feb  2 01:10:34.882: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6glrh" in namespace "azuredisk-1904" to be "Succeeded or Failed"
Feb  2 01:10:34.916: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 34.050204ms
Feb  2 01:10:36.949: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067022509s
Feb  2 01:10:38.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068166526s
Feb  2 01:10:40.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067907537s
Feb  2 01:10:42.949: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.06688088s
Feb  2 01:10:44.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067339259s
... skipping 101 lines ...
Feb  2 01:14:08.952: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=true. Elapsed: 3m34.069548019s
Feb  2 01:14:10.952: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=true. Elapsed: 3m36.069169763s
Feb  2 01:14:12.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.068085838s
Feb  2 01:14:14.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.068825276s
Feb  2 01:14:16.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m42.068509919s
STEP: Saw pod success 02/02/23 01:14:16.951
Feb  2 01:14:16.951: INFO: Pod "azuredisk-volume-tester-6glrh" satisfied condition "Succeeded or Failed"
Feb  2 01:14:16.951: INFO: deleting Pod "azuredisk-1904"/"azuredisk-volume-tester-6glrh"
Feb  2 01:14:17.009: INFO: Pod azuredisk-volume-tester-6glrh has the following logs: ´╗┐hello world

STEP: Deleting pod azuredisk-volume-tester-6glrh in namespace azuredisk-1904 02/02/23 01:14:17.009
Feb  2 01:14:17.139: INFO: deleting PVC "azuredisk-1904"/"pvc-sgwd4"
Feb  2 01:14:17.139: INFO: Deleting PersistentVolumeClaim "pvc-sgwd4"
... skipping 38 lines ...
    Feb  2 01:10:27.446: INFO: PersistentVolumeClaim pvc-sgwd4 found and phase=Bound (2.067192522s)
    STEP: checking the PVC 02/02/23 01:10:27.446
    STEP: validating provisioned PV 02/02/23 01:10:27.478
    STEP: checking the PV 02/02/23 01:10:27.51
    STEP: attaching disk to node#0 02/02/23 01:10:27.554
    STEP: deploying the pod 02/02/23 01:10:34.835
    STEP: checking that the pod's command exits with no error 02/02/23 01:10:34.882
    Feb  2 01:10:34.882: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6glrh" in namespace "azuredisk-1904" to be "Succeeded or Failed"
    Feb  2 01:10:34.916: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 34.050204ms
    Feb  2 01:10:36.949: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067022509s
    Feb  2 01:10:38.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.068166526s
    Feb  2 01:10:40.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.067907537s
    Feb  2 01:10:42.949: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.06688088s
    Feb  2 01:10:44.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.067339259s
... skipping 101 lines ...
    Feb  2 01:14:08.952: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=true. Elapsed: 3m34.069548019s
    Feb  2 01:14:10.952: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=true. Elapsed: 3m36.069169763s
    Feb  2 01:14:12.950: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.068085838s
    Feb  2 01:14:14.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.068825276s
    Feb  2 01:14:16.951: INFO: Pod "azuredisk-volume-tester-6glrh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 3m42.068509919s
    STEP: Saw pod success 02/02/23 01:14:16.951
    Feb  2 01:14:16.951: INFO: Pod "azuredisk-volume-tester-6glrh" satisfied condition "Succeeded or Failed"
    Feb  2 01:14:16.951: INFO: deleting Pod "azuredisk-1904"/"azuredisk-volume-tester-6glrh"
    Feb  2 01:14:17.009: INFO: Pod azuredisk-volume-tester-6glrh has the following logs: ´╗┐hello world

    STEP: Deleting pod azuredisk-volume-tester-6glrh in namespace azuredisk-1904 02/02/23 01:14:17.009
    Feb  2 01:14:17.139: INFO: deleting PVC "azuredisk-1904"/"pvc-sgwd4"
    Feb  2 01:14:17.139: INFO: Deleting PersistentVolumeClaim "pvc-sgwd4"
... skipping 150 lines ...
  << End Captured GinkgoWriter Output

  test case not supported by Windows clusters
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26

  There were additional failures detected after the initial failure:
    [FAILED]
    pre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: {
      "error": {

        "code": "NotFound",
        "message": "Disk single-shared-disk is not found."
      }
    }
    In [AfterEach] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490
------------------------------
... skipping 27 lines ...
  << End Captured GinkgoWriter Output

  test case not supported by Windows clusters
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26

  There were additional failures detected after the initial failure:
    [FAILED]
    pre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: {
      "error": {

        "code": "NotFound",
        "message": "Disk single-shared-disk is not found."
      }
    }
    In [AfterEach] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490
------------------------------
... skipping 27 lines ...
  << End Captured GinkgoWriter Output

  test case is only available for csi driver
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:395

  There were additional failures detected after the initial failure:
    [FAILED]
    pre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: {
      "error": {

        "code": "NotFound",
        "message": "Disk single-shared-disk is not found."
      }
    }
    In [AfterEach] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490
------------------------------
... skipping 4 lines ...
Feb  2 01:14:54.498: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: Building a namespace api object, basename azuredisk 02/02/23 01:14:54.499
STEP: Waiting for a default service account to be provisioned in namespace 02/02/23 01:14:54.609
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 02/02/23 01:14:54.671
I0202 01:14:54.733288   41944 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com
STEP: deploying the pod 02/02/23 01:14:54.78
STEP: checking that the pod's command exits with no error 02/02/23 01:14:54.822
Feb  2 01:14:54.822: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mskv2" in namespace "azuredisk-1829" to be "Succeeded or Failed"
Feb  2 01:14:54.854: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.102773ms
Feb  2 01:14:56.887: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064977695s
Feb  2 01:14:58.886: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064055952s
Feb  2 01:15:00.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 6.06614316s
Feb  2 01:15:02.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 8.066508512s
Feb  2 01:15:04.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 10.066551098s
Feb  2 01:15:06.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=false. Elapsed: 12.066632336s
Feb  2 01:15:08.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.066743026s
STEP: Saw pod success 02/02/23 01:15:08.892
Feb  2 01:15:08.892: INFO: Pod "azuredisk-volume-tester-mskv2" satisfied condition "Succeeded or Failed"
Feb  2 01:15:08.892: INFO: deleting Pod "azuredisk-1829"/"azuredisk-volume-tester-mskv2"
Feb  2 01:15:08.949: INFO: Pod azuredisk-volume-tester-mskv2 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-mskv2 in namespace azuredisk-1829 02/02/23 01:15:08.949
STEP: Destroying namespace "azuredisk-1829" for this suite. 02/02/23 01:15:08.995
------------------------------
... skipping 10 lines ...
    Feb  2 01:14:54.498: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
    STEP: Building a namespace api object, basename azuredisk 02/02/23 01:14:54.499
    STEP: Waiting for a default service account to be provisioned in namespace 02/02/23 01:14:54.609
    STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 02/02/23 01:14:54.671
    I0202 01:14:54.733288   41944 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com
    STEP: deploying the pod 02/02/23 01:14:54.78
    STEP: checking that the pod's command exits with no error 02/02/23 01:14:54.822
    Feb  2 01:14:54.822: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mskv2" in namespace "azuredisk-1829" to be "Succeeded or Failed"
    Feb  2 01:14:54.854: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.102773ms
    Feb  2 01:14:56.887: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064977695s
    Feb  2 01:14:58.886: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064055952s
    Feb  2 01:15:00.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 6.06614316s
    Feb  2 01:15:02.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 8.066508512s
    Feb  2 01:15:04.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=true. Elapsed: 10.066551098s
    Feb  2 01:15:06.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Running", Reason="", readiness=false. Elapsed: 12.066632336s
    Feb  2 01:15:08.888: INFO: Pod "azuredisk-volume-tester-mskv2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.066743026s
    STEP: Saw pod success 02/02/23 01:15:08.892
    Feb  2 01:15:08.892: INFO: Pod "azuredisk-volume-tester-mskv2" satisfied condition "Succeeded or Failed"
    Feb  2 01:15:08.892: INFO: deleting Pod "azuredisk-1829"/"azuredisk-volume-tester-mskv2"
    Feb  2 01:15:08.949: INFO: Pod azuredisk-volume-tester-mskv2 has the following logs: hello world

    STEP: Deleting pod azuredisk-volume-tester-mskv2 in namespace azuredisk-1829 02/02/23 01:15:08.949
    STEP: Destroying namespace "azuredisk-1829" for this suite. 02/02/23 01:15:08.995
  << End Captured GinkgoWriter Output
... skipping 17 lines ...
Feb  2 01:15:11.392: INFO: PersistentVolumeClaim pvc-9rljt found but phase is Pending instead of Bound.
Feb  2 01:15:13.424: INFO: PersistentVolumeClaim pvc-9rljt found and phase=Bound (4.097933297s)
STEP: checking the PVC 02/02/23 01:15:13.424
STEP: validating provisioned PV 02/02/23 01:15:13.456
STEP: checking the PV 02/02/23 01:15:13.487
STEP: deploying the pod 02/02/23 01:15:13.53
STEP: checking that the pod's command exits with no error 02/02/23 01:15:13.569
Feb  2 01:15:13.569: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lrnzm" in namespace "azuredisk-2229" to be "Succeeded or Failed"
Feb  2 01:15:13.604: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 34.417177ms
Feb  2 01:15:15.637: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067523403s
Feb  2 01:15:17.636: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.067075318s
Feb  2 01:15:19.638: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.068580807s
Feb  2 01:15:21.637: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.067526955s
Feb  2 01:15:23.638: INFO: Pod "azuredisk-volume-tester-lrnzm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.069121295s
... skipping 14 lines ...