kubernetes-sigs/azuredisk-csi-driver PR #1712 pull-azuredisk-csi-driver-e2e-capz-windows-2019-mainv2 #1620928614709071872
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | edreed: [V2] build: disable provenance attestation to work around docker issue |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h14m |
| Revision | 5ea95d0ebda60f445b259c9f22f01aee679e594a |
| Refs |
1712 |
... skipping 810 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 229 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 160k 0 --:--:-- --:--:-- --:--:-- 160k 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c not found: manifest unknown: manifest tagged by "latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c" 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-01T23:53:15Z -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 239 lines ... #9 exporting to image #9 pushing layers 2.5s done #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64@sha256:20d672f89e6e53be3121a099cc60b8a6b3c552175a42b7182b313a1056c87e77 #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64@sha256:20d672f89e6e53be3121a099cc60b8a6b3c552175a42b7182b313a1056c87e77 0.5s done #9 DONE 10.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.driverVersion=latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-01T23:56:47Z -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 117 lines ... #8 exporting config sha256:a9eca5fcc350b0026083c9628198d43fe9903173842d933b00acc3dc5904b7a9 0.0s done #8 pushing layers #8 pushing layers 1.9s done #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64@sha256:ac35cc29dbda7c0cfde2dd0fb973bb18ee29e970bf7b6ce89aa8f0444840416f #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64@sha256:ac35cc29dbda7c0cfde2dd0fb973bb18ee29e970bf7b6ce89aa8f0444840416f 0.4s done #8 DONE 9.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' 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 75 lines ... #10 exporting config sha256:f683e16ad926051cfc553b5e6ac872b72d79c6f83d8facf93fbdbf7c90ac93c7 0.0s done #10 pushing layers #10 pushing layers 1.8s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-1809-amd64@sha256:af1367e3035b26cbe1a0dcbc7bae917c7519643467b41005fc44b9b927eeb25c #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-1809-amd64@sha256:af1367e3035b26cbe1a0dcbc7bae917c7519643467b41005fc44b9b927eeb25c 0.3s done #10 DONE 9.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 69 lines ... #10 exporting config sha256:9bfb4dc08325133ffbcf5f70f4e017d063c18aa72967631b71e8cdf454c17c42 0.0s done #10 pushing layers #10 pushing layers 1.6s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-20H2-amd64@sha256:b81cc7e8b1abc8c0757c815232cab90b59fd6ba1ee6b0d100ece139d98287667 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-20H2-amd64@sha256:b81cc7e8b1abc8c0757c815232cab90b59fd6ba1ee6b0d100ece139d98287667 0.3s done #10 DONE 8.6s 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 77 lines ... #10 exporting config sha256:76d56637a51c188996aa63487d19065fcfa56a7a1cc3e64e5c9cedf0669878d7 0.0s done #10 pushing layers #10 pushing layers 1.6s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-ltsc2022-amd64@sha256:049bf83cf87e477b2aae658bd24a19121949c43ef95f580efa59b1f02759821d #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-ltsc2022-amd64@sha256:049bf83cf87e477b2aae658bd24a19121949c43ef95f580efa59b1f02759821d 0.4s done #10 DONE 8.8s 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64 capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-1809-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-20H2-amd64 capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-windows-ltsc2022-amd64 Created manifest list capzci.azurecr.io/azuredisk-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c # 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c not found: manifest unknown: manifest tagged by "latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c" 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.3s done #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64@sha256:1c91e0ad75ff250c9bba9ff419fba99d25b3f1365b680725baadcf202c511087 #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64@sha256:1c91e0ad75ff250c9bba9ff419fba99d25b3f1365b680725baadcf202c511087 0.4s done #8 DONE 5.7s 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-02T00:02:41Z -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 36 lines ... #7 exporting config sha256:75fce4f5b037b691d308aecec558341ed7f76182743b96566d1a723eafacaa6f 0.0s done #7 pushing layers #7 pushing layers 1.8s done #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64@sha256:d78d3c70f46d1bee31eccd65d1f941ae08040a5a8cf111af46346351d1eae9ae #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64@sha256:d78d3c70f46d1bee31eccd65d1f941ae08040a5a8cf111af46346351d1eae9ae 0.4s done #7 DONE 4.8s 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-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-amd64 capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c-linux-arm64 Created manifest list capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c docker manifest push --purge capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c sha256:5e0f14456d576c765ed9a0874895225ac2b0cb7b2deb753adfa79c316ce098ad docker manifest inspect capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-3d84ccaf7bb075abd5912e16e39b09b4d5f88f6c ... skipping 886 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 324 lines ... Feb 2 00:05:39.712: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-smlx2] to have phase Bound Feb 2 00:05:39.818: INFO: PersistentVolumeClaim pvc-smlx2 found and phase=Bound (106.909802ms) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:05:39.818[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:05:39.921[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:05:40.024[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:05:40.024[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/02/23 00:05:40.131[0m Feb 2 00:05:40.131: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-ssqrw" in namespace "azuredisk-4046" to be "Error status code" Feb 2 00:05:40.234: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 102.469385ms Feb 2 00:05:42.338: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207004918s Feb 2 00:05:44.344: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.212779196s Feb 2 00:05:46.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207559685s Feb 2 00:05:48.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.207468461s Feb 2 00:05:50.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208113028s ... skipping 108 lines ... Feb 2 00:09:28.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 3m48.209094515s Feb 2 00:09:30.338: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m50.206849296s Feb 2 00:09:32.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m52.207890113s Feb 2 00:09:34.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m54.207471112s Feb 2 00:09:36.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.207832152s Feb 2 00:09:38.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.208618113s Feb 2 00:09:40.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Failed", Reason="", readiness=false. Elapsed: 4m0.208912671s [1mSTEP:[0m Saw pod failure [38;5;243m02/02/23 00:09:40.34[0m Feb 2 00:09:40.340: INFO: Pod "azuredisk-volume-tester-ssqrw" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/02/23 00:09:40.34[0m Feb 2 00:09:40.471: INFO: deleting Pod "azuredisk-4046"/"azuredisk-volume-tester-ssqrw" Feb 2 00:09:40.578: INFO: Pod azuredisk-volume-tester-ssqrw 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 00:05:39.712: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-smlx2] to have phase Bound Feb 2 00:05:39.818: INFO: PersistentVolumeClaim pvc-smlx2 found and phase=Bound (106.909802ms) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:05:39.818[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:05:39.921[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:05:40.024[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:05:40.024[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/02/23 00:05:40.131[0m Feb 2 00:05:40.131: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-ssqrw" in namespace "azuredisk-4046" to be "Error status code" Feb 2 00:05:40.234: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 102.469385ms Feb 2 00:05:42.338: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207004918s Feb 2 00:05:44.344: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.212779196s Feb 2 00:05:46.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.207559685s Feb 2 00:05:48.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.207468461s Feb 2 00:05:50.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208113028s ... skipping 108 lines ... Feb 2 00:09:28.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Pending", Reason="", readiness=false. Elapsed: 3m48.209094515s Feb 2 00:09:30.338: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m50.206849296s Feb 2 00:09:32.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m52.207890113s Feb 2 00:09:34.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=true. Elapsed: 3m54.207471112s Feb 2 00:09:36.339: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.207832152s Feb 2 00:09:38.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.208618113s Feb 2 00:09:40.340: INFO: Pod "azuredisk-volume-tester-ssqrw": Phase="Failed", Reason="", readiness=false. Elapsed: 4m0.208912671s [1mSTEP:[0m Saw pod failure [38;5;243m02/02/23 00:09:40.34[0m Feb 2 00:09:40.340: INFO: Pod "azuredisk-volume-tester-ssqrw" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/02/23 00:09:40.34[0m Feb 2 00:09:40.471: INFO: deleting Pod "azuredisk-4046"/"azuredisk-volume-tester-ssqrw" Feb 2 00:09:40.578: INFO: Pod azuredisk-volume-tester-ssqrw 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 00:10:49.612: INFO: PersistentVolumeClaim pvc-s9ds4 found and phase=Bound (102.780028ms) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:10:49.612[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:10:49.715[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:10:49.817[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m02/02/23 00:10:49.941[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:10:58.909[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:10:59.016[0m Feb 2 00:10:59.016: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fx2qk" in namespace "azuredisk-2041" to be "Succeeded or Failed" Feb 2 00:10:59.119: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 102.642866ms Feb 2 00:11:01.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207171567s Feb 2 00:11:03.223: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.207048018s Feb 2 00:11:05.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208010361s Feb 2 00:11:07.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.207076779s Feb 2 00:11:09.223: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206478326s ... skipping 25 lines ... Feb 2 00:12:01.226: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=true. Elapsed: 1m2.209727689s Feb 2 00:12:03.225: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=true. Elapsed: 1m4.208114324s Feb 2 00:12:05.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.207836385s Feb 2 00:12:07.226: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.20914153s Feb 2 00:12:09.225: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m10.208446745s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:12:09.225[0m Feb 2 00:12:09.225: INFO: Pod "azuredisk-volume-tester-fx2qk" satisfied condition "Succeeded or Failed" Feb 2 00:12:09.225: INFO: deleting Pod "azuredisk-2041"/"azuredisk-volume-tester-fx2qk" Feb 2 00:12:09.344: INFO: Pod azuredisk-volume-tester-fx2qk has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-fx2qk in namespace azuredisk-2041 [38;5;243m02/02/23 00:12:09.344[0m Feb 2 00:12:09.674: INFO: deleting PVC "azuredisk-2041"/"pvc-s9ds4" Feb 2 00:12:09.674: INFO: Deleting PersistentVolumeClaim "pvc-s9ds4" ... skipping 38 lines ... Feb 2 00:10:49.612: INFO: PersistentVolumeClaim pvc-s9ds4 found and phase=Bound (102.780028ms) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:10:49.612[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:10:49.715[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:10:49.817[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m02/02/23 00:10:49.941[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:10:58.909[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:10:59.016[0m Feb 2 00:10:59.016: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fx2qk" in namespace "azuredisk-2041" to be "Succeeded or Failed" Feb 2 00:10:59.119: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 102.642866ms Feb 2 00:11:01.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.207171567s Feb 2 00:11:03.223: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.207048018s Feb 2 00:11:05.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.208010361s Feb 2 00:11:07.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.207076779s Feb 2 00:11:09.223: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206478326s ... skipping 25 lines ... Feb 2 00:12:01.226: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=true. Elapsed: 1m2.209727689s Feb 2 00:12:03.225: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=true. Elapsed: 1m4.208114324s Feb 2 00:12:05.224: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.207836385s Feb 2 00:12:07.226: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.20914153s Feb 2 00:12:09.225: INFO: Pod "azuredisk-volume-tester-fx2qk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m10.208446745s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:12:09.225[0m Feb 2 00:12:09.225: INFO: Pod "azuredisk-volume-tester-fx2qk" satisfied condition "Succeeded or Failed" Feb 2 00:12:09.225: INFO: deleting Pod "azuredisk-2041"/"azuredisk-volume-tester-fx2qk" Feb 2 00:12:09.344: INFO: Pod azuredisk-volume-tester-fx2qk has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-fx2qk in namespace azuredisk-2041 [38;5;243m02/02/23 00:12:09.344[0m Feb 2 00:12:09.674: INFO: deleting PVC "azuredisk-2041"/"pvc-s9ds4" Feb 2 00:12:09.674: INFO: Deleting PersistentVolumeClaim "pvc-s9ds4" ... skipping 151 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case not supported by Windows clusters[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-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." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 27 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case not supported by Windows clusters[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/utils/testutil/env_utils.go:26[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-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." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 27 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for csi driver[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:395[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-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." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 4 lines ... Feb 2 00:12:58.977: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m02/02/23 00:12:58.978[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m02/02/23 00:12:59.294[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m02/02/23 00:12:59.499[0m I0202 00:12:59.705356 41910 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:12:59.818[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:12:59.931[0m Feb 2 00:12:59.931: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-w6k5q" in namespace "azuredisk-2202" to be "Succeeded or Failed" Feb 2 00:13:00.035: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 104.129315ms Feb 2 00:13:02.139: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208188025s Feb 2 00:13:04.139: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.207610325s Feb 2 00:13:06.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 6.209294502s Feb 2 00:13:08.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 8.210664036s Feb 2 00:13:10.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 10.210762063s Feb 2 00:13:12.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=false. Elapsed: 12.210942799s Feb 2 00:13:14.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=false. Elapsed: 14.209187578s Feb 2 00:13:16.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.208973022s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:13:16.14[0m Feb 2 00:13:16.140: INFO: Pod "azuredisk-volume-tester-w6k5q" satisfied condition "Succeeded or Failed" Feb 2 00:13:16.140: INFO: deleting Pod "azuredisk-2202"/"azuredisk-volume-tester-w6k5q" Feb 2 00:13:16.255: INFO: Pod azuredisk-volume-tester-w6k5q has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-w6k5q in namespace azuredisk-2202 [38;5;243m02/02/23 00:13:16.255[0m [1mSTEP:[0m Destroying namespace "azuredisk-2202" for this suite. [38;5;243m02/02/23 00:13:16.372[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Feb 2 00:12:58.977: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m02/02/23 00:12:58.978[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m02/02/23 00:12:59.294[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m02/02/23 00:12:59.499[0m I0202 00:12:59.705356 41910 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:12:59.818[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:12:59.931[0m Feb 2 00:12:59.931: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-w6k5q" in namespace "azuredisk-2202" to be "Succeeded or Failed" Feb 2 00:13:00.035: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 104.129315ms Feb 2 00:13:02.139: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.208188025s Feb 2 00:13:04.139: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Pending", Reason="", readiness=false. Elapsed: 4.207610325s Feb 2 00:13:06.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 6.209294502s Feb 2 00:13:08.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 8.210664036s Feb 2 00:13:10.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=true. Elapsed: 10.210762063s Feb 2 00:13:12.142: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=false. Elapsed: 12.210942799s Feb 2 00:13:14.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Running", Reason="", readiness=false. Elapsed: 14.209187578s Feb 2 00:13:16.140: INFO: Pod "azuredisk-volume-tester-w6k5q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.208973022s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:13:16.14[0m Feb 2 00:13:16.140: INFO: Pod "azuredisk-volume-tester-w6k5q" satisfied condition "Succeeded or Failed" Feb 2 00:13:16.140: INFO: deleting Pod "azuredisk-2202"/"azuredisk-volume-tester-w6k5q" Feb 2 00:13:16.255: INFO: Pod azuredisk-volume-tester-w6k5q has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-w6k5q in namespace azuredisk-2202 [38;5;243m02/02/23 00:13:16.255[0m [1mSTEP:[0m Destroying namespace "azuredisk-2202" for this suite. [38;5;243m02/02/23 00:13:16.372[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Feb 2 00:13:19.638: INFO: PersistentVolumeClaim pvc-5j6dm found but phase is Pending instead of Bound. Feb 2 00:13:21.742: INFO: PersistentVolumeClaim pvc-5j6dm found and phase=Bound (4.310642952s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:13:21.742[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:13:21.846[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:13:21.95[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:13:22.063[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:13:22.172[0m Feb 2 00:13:22.172: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ws5r5" in namespace "azuredisk-2359" to be "Succeeded or Failed" Feb 2 00:13:22.279: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 106.761977ms Feb 2 00:13:24.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211550122s Feb 2 00:13:26.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.211779422s Feb 2 00:13:28.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211578655s Feb 2 00:13:30.383: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.211271028s Feb 2 00:13:32.386: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213642297s ... skipping 17 lines ... Feb 2 00:14:08.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=true. Elapsed: 46.212256604s Feb 2 00:14:10.385: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=true. Elapsed: 48.213029786s Feb 2 00:14:12.385: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=false. Elapsed: 50.212818996s Feb 2 00:14:14.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=false. Elapsed: 52.212252877s Feb 2 00:14:16.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.21231867s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:14:16.385[0m Feb 2 00:14:16.385: INFO: Pod "azuredisk-volume-tester-ws5r5" satisfied condition "Succeeded or Failed" Feb 2 00:14:16.385: INFO: deleting Pod "azuredisk-2359"/"azuredisk-volume-tester-ws5r5" Feb 2 00:14:16.498: INFO: Pod azuredisk-volume-tester-ws5r5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ws5r5 in namespace azuredisk-2359 [38;5;243m02/02/23 00:14:16.498[0m Feb 2 00:14:16.617: INFO: deleting PVC "azuredisk-2359"/"pvc-5j6dm" Feb 2 00:14:16.617: INFO: Deleting PersistentVolumeClaim "pvc-5j6dm" ... skipping 38 lines ... Feb 2 00:13:19.638: INFO: PersistentVolumeClaim pvc-5j6dm found but phase is Pending instead of Bound. Feb 2 00:13:21.742: INFO: PersistentVolumeClaim pvc-5j6dm found and phase=Bound (4.310642952s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:13:21.742[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:13:21.846[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:13:21.95[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:13:22.063[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:13:22.172[0m Feb 2 00:13:22.172: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-ws5r5" in namespace "azuredisk-2359" to be "Succeeded or Failed" Feb 2 00:13:22.279: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 106.761977ms Feb 2 00:13:24.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.211550122s Feb 2 00:13:26.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.211779422s Feb 2 00:13:28.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211578655s Feb 2 00:13:30.383: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.211271028s Feb 2 00:13:32.386: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.213642297s ... skipping 17 lines ... Feb 2 00:14:08.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=true. Elapsed: 46.212256604s Feb 2 00:14:10.385: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=true. Elapsed: 48.213029786s Feb 2 00:14:12.385: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=false. Elapsed: 50.212818996s Feb 2 00:14:14.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Running", Reason="", readiness=false. Elapsed: 52.212252877s Feb 2 00:14:16.384: INFO: Pod "azuredisk-volume-tester-ws5r5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.21231867s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:14:16.385[0m Feb 2 00:14:16.385: INFO: Pod "azuredisk-volume-tester-ws5r5" satisfied condition "Succeeded or Failed" Feb 2 00:14:16.385: INFO: deleting Pod "azuredisk-2359"/"azuredisk-volume-tester-ws5r5" Feb 2 00:14:16.498: INFO: Pod azuredisk-volume-tester-ws5r5 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-ws5r5 in namespace azuredisk-2359 [38;5;243m02/02/23 00:14:16.498[0m Feb 2 00:14:16.617: INFO: deleting PVC "azuredisk-2359"/"pvc-5j6dm" Feb 2 00:14:16.617: INFO: Deleting PersistentVolumeClaim "pvc-5j6dm" ... skipping 183 lines ... Feb 2 00:21:20.418: INFO: PersistentVolumeClaim pvc-cc2d2 found and phase=Bound (4.307681289s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:21:20.418[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:21:20.521[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:21:20.625[0m I0202 00:21:20.625431 41910 resource_setup.go:89] adding PV (pvc-55be25d9-f398-4345-b2a5-df0a94e45783) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:21:20.77[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:21:20.894[0m Feb 2 00:21:20.894: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m5m2f" in namespace "azuredisk-7675" to be "Succeeded or Failed" Feb 2 00:21:21.007: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 113.103785ms Feb 2 00:21:23.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223543013s Feb 2 00:21:25.119: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.224827044s Feb 2 00:21:27.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.223797353s Feb 2 00:21:29.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223363546s Feb 2 00:21:31.119: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.224710617s ... skipping 20 lines ... Feb 2 00:22:13.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=true. Elapsed: 52.223063458s Feb 2 00:22:15.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=true. Elapsed: 54.224385565s Feb 2 00:22:17.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=false. Elapsed: 56.222672089s Feb 2 00:22:19.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=false. Elapsed: 58.223920833s Feb 2 00:22:21.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m0.222841213s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:22:21.117[0m Feb 2 00:22:21.117: INFO: Pod "azuredisk-volume-tester-m5m2f" satisfied condition "Succeeded or Failed" Feb 2 00:22:21.117: INFO: deleting Pod "azuredisk-7675"/"azuredisk-volume-tester-m5m2f" Feb 2 00:22:21.245: INFO: Pod azuredisk-volume-tester-m5m2f has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m5m2f in namespace azuredisk-7675 [38;5;243m02/02/23 00:22:21.245[0m Feb 2 00:22:21.364: INFO: deleting PVC "azuredisk-7675"/"pvc-cc2d2" Feb 2 00:22:21.364: INFO: Deleting PersistentVolumeClaim "pvc-cc2d2" ... skipping 85 lines ... Feb 2 00:21:20.418: INFO: PersistentVolumeClaim pvc-cc2d2 found and phase=Bound (4.307681289s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 00:21:20.418[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 00:21:20.521[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 00:21:20.625[0m I0202 00:21:20.625431 41910 resource_setup.go:89] adding PV (pvc-55be25d9-f398-4345-b2a5-df0a94e45783) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 00:21:20.77[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 00:21:20.894[0m Feb 2 00:21:20.894: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m5m2f" in namespace "azuredisk-7675" to be "Succeeded or Failed" Feb 2 00:21:21.007: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 113.103785ms Feb 2 00:21:23.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223543013s Feb 2 00:21:25.119: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.224827044s Feb 2 00:21:27.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.223797353s Feb 2 00:21:29.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.223363546s Feb 2 00:21:31.119: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.224710617s ... skipping 20 lines ... Feb 2 00:22:13.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=true. Elapsed: 52.223063458s Feb 2 00:22:15.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=true. Elapsed: 54.224385565s Feb 2 00:22:17.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=false. Elapsed: 56.222672089s Feb 2 00:22:19.118: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Running", Reason="", readiness=false. Elapsed: 58.223920833s Feb 2 00:22:21.117: INFO: Pod "azuredisk-volume-tester-m5m2f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m0.222841213s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 00:22:21.117[0m Feb 2 00:22:21.117: INFO: Pod "azuredisk-volume-tester-m5m2f" satisfied condition "Succeeded or Failed" Feb 2 00:22:21.117: INFO: deleting Pod "azuredisk-7675"/"azuredisk-volume-tester-m5m2f" Feb 2 00:22:21.245: INFO: Pod azuredisk-volume-tester-m5m2f has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-m5m2f in namespace azuredisk-7675 [38;5;243m02/02/23 00:22:21.245[0m Feb 2 00:22:21.364: INFO: deleting PVC "azuredisk-7675"/"pvc-cc2d2" Feb 2 00:22:21.364: INFO: Deleting PersistentVolumeClaim "pvc-cc2d2" ... skipping 518 lines ...