kubernetes-sigs/azuredisk-csi-driver PR #1712 pull-azuredisk-csi-driver-e2e-capz-mainv2 #1620943723258974208
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 | 55m57s |
| Revision | fed380e17e859876de9b04df4872228ffc5570f5 |
| Refs |
1712 |
... skipping 803 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 223 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 120k 0 --:--:-- --:--:-- --:--:-- 120k 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:54:58Z -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 240 lines ... #9 exporting to image #9 pushing layers 2.1s done #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:7f966d9cea9dc3e5d0863372acbb3e7f2e7019a87e2ba9671477387a2bde77d3 #9 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:7f966d9cea9dc3e5d0863372acbb3e7f2e7019a87e2ba9671477387a2bde77d3 0.4s done #9 DONE 6.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' 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:58:29Z -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:fd801483074849c2918961f8fe60112da68b6dd89f72eecdda8e1e541413c960 0.0s done #8 pushing layers #8 pushing layers 2.1s done #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:2a4aa5711bf5bebc38157814f1bfdfc953f0fba259d97bd644ba441da153f7ca #8 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:2a4aa5711bf5bebc38157814f1bfdfc953f0fba259d97bd644ba441da153f7ca 0.5s done #8 DONE 7.3s 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 77 lines ... #10 exporting config sha256:1ba827fcfe3e620d18b79a2bf56cfb7971a45f4242864ebfc14a9c6193011465 0.0s done #10 pushing layers #10 pushing layers 1.9s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-1809-amd64@sha256:dcaa756d69615e57d33a977ebf0cdfb616addb31d582006329443ea7fbf3b1b7 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-1809-amd64@sha256:dcaa756d69615e57d33a977ebf0cdfb616addb31d582006329443ea7fbf3b1b7 0.3s done #10 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' docker buildx build . \ --pull \ --output=type=registry \ --platform="windows/amd64" \ ... skipping 69 lines ... #10 exporting config sha256:55a76dfd049c65a6258d6f75941f84f0838e71914059cab9a13febff7aad1007 0.0s done #10 pushing layers #10 pushing layers 2.3s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-20H2-amd64@sha256:7a75975b452171123ace851209ebc90246b6840f02a0692a9a8b497f55c78442 #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-20H2-amd64@sha256:7a75975b452171123ace851209ebc90246b6840f02a0692a9a8b497f55c78442 0.3s done #10 DONE 7.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 73 lines ... #10 exporting config sha256:1036a74b549549bfc9f3b107e4114e504bcd10bc16d7a3582a1096e237137977 0.0s done #10 pushing layers #10 pushing layers 1.6s done #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-ltsc2022-amd64@sha256:a034a6eba0813ef255317c1c979d2c2c7a52359cca36b1521ff82d40d09c03af #10 pushing manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-windows-ltsc2022-amd64@sha256:a034a6eba0813ef255317c1c979d2c2c7a52359cca36b1521ff82d40d09c03af 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' 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.1s done #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:a6897bf11db878af538d5d8ab3f71a0011b628f411a13afccbb3213cce2c68d4 #8 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-amd64@sha256:a6897bf11db878af538d5d8ab3f71a0011b628f411a13afccbb3213cce2c68d4 0.4s done #8 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' 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:09Z -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:1972b1b5c37774d248bd92df9ecc6613b70cc0d9691691fedeab66555fb41158 0.0s done #7 pushing layers #7 pushing layers 1.8s done #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:f9aa3456be9183494ed6cc64cf1acb054581465e0fc82a1440e2fbe38971640b #7 pushing manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3-linux-arm64@sha256:f9aa3456be9183494ed6cc64cf1acb054581465e0fc82a1440e2fbe38971640b 0.4s done #7 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' 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:95622d6563cdda60b6f00fd3fbb35e1a8236eb4ca45fb785f5067defc807aaca docker manifest inspect capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-09aefd42c7b32eeba843ab488fe9a4686ebfb2e3 ... skipping 821 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 1069 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 283 lines ... Feb 2 01:07:17.150: 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 01:07:17.151[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m02/02/23 01:07:17.723[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m02/02/23 01:07:17.93[0m I0202 01:07:18.138075 42332 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:07:18.302[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:07:18.408[0m Feb 2 01:07:18.408: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-rglf8" in namespace "azuredisk-2000" to be "Succeeded or Failed" Feb 2 01:07:18.511: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Pending", Reason="", readiness=false. Elapsed: 102.94584ms Feb 2 01:07:20.621: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Running", Reason="", readiness=true. Elapsed: 2.213118605s Feb 2 01:07:22.621: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Running", Reason="", readiness=false. Elapsed: 4.212884085s Feb 2 01:07:24.622: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.214389389s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:07:24.623[0m Feb 2 01:07:24.623: INFO: Pod "azuredisk-volume-tester-rglf8" satisfied condition "Succeeded or Failed" Feb 2 01:07:24.623: INFO: deleting Pod "azuredisk-2000"/"azuredisk-volume-tester-rglf8" Feb 2 01:07:24.752: INFO: Pod azuredisk-volume-tester-rglf8 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-rglf8 in namespace azuredisk-2000 [38;5;243m02/02/23 01:07:24.752[0m [1mSTEP:[0m Destroying namespace "azuredisk-2000" for this suite. [38;5;243m02/02/23 01:07:24.868[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Feb 2 01:07:17.150: 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 01:07:17.151[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m02/02/23 01:07:17.723[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m02/02/23 01:07:17.93[0m I0202 01:07:18.138075 42332 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:07:18.302[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:07:18.408[0m Feb 2 01:07:18.408: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-rglf8" in namespace "azuredisk-2000" to be "Succeeded or Failed" Feb 2 01:07:18.511: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Pending", Reason="", readiness=false. Elapsed: 102.94584ms Feb 2 01:07:20.621: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Running", Reason="", readiness=true. Elapsed: 2.213118605s Feb 2 01:07:22.621: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Running", Reason="", readiness=false. Elapsed: 4.212884085s Feb 2 01:07:24.622: INFO: Pod "azuredisk-volume-tester-rglf8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.214389389s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:07:24.623[0m Feb 2 01:07:24.623: INFO: Pod "azuredisk-volume-tester-rglf8" satisfied condition "Succeeded or Failed" Feb 2 01:07:24.623: INFO: deleting Pod "azuredisk-2000"/"azuredisk-volume-tester-rglf8" Feb 2 01:07:24.752: INFO: Pod azuredisk-volume-tester-rglf8 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-rglf8 in namespace azuredisk-2000 [38;5;243m02/02/23 01:07:24.752[0m [1mSTEP:[0m Destroying namespace "azuredisk-2000" for this suite. [38;5;243m02/02/23 01:07:24.868[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Feb 2 01:07:28.116: INFO: PersistentVolumeClaim pvc-mnx47 found but phase is Pending instead of Bound. Feb 2 01:07:30.219: INFO: PersistentVolumeClaim pvc-mnx47 found and phase=Bound (4.311490921s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 01:07:30.219[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 01:07:30.322[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 01:07:30.425[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:07:30.577[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:07:30.683[0m Feb 2 01:07:30.683: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-587vb" in namespace "azuredisk-5135" to be "Succeeded or Failed" Feb 2 01:07:30.788: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 104.556714ms Feb 2 01:07:32.893: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209800679s Feb 2 01:07:34.894: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.210211454s Feb 2 01:07:36.895: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211220196s Feb 2 01:07:38.893: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.209164637s Feb 2 01:07:40.892: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208346133s Feb 2 01:07:42.894: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210828237s Feb 2 01:07:44.892: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.208748698s Feb 2 01:07:46.897: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.213979416s Feb 2 01:07:48.899: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.215186876s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:07:48.899[0m Feb 2 01:07:48.899: INFO: Pod "azuredisk-volume-tester-587vb" satisfied condition "Succeeded or Failed" Feb 2 01:07:48.899: INFO: deleting Pod "azuredisk-5135"/"azuredisk-volume-tester-587vb" Feb 2 01:07:49.003: INFO: Pod azuredisk-volume-tester-587vb has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-587vb in namespace azuredisk-5135 [38;5;243m02/02/23 01:07:49.003[0m Feb 2 01:07:49.116: INFO: deleting PVC "azuredisk-5135"/"pvc-mnx47" Feb 2 01:07:49.116: INFO: Deleting PersistentVolumeClaim "pvc-mnx47" ... skipping 34 lines ... Feb 2 01:07:28.116: INFO: PersistentVolumeClaim pvc-mnx47 found but phase is Pending instead of Bound. Feb 2 01:07:30.219: INFO: PersistentVolumeClaim pvc-mnx47 found and phase=Bound (4.311490921s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 01:07:30.219[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 01:07:30.322[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 01:07:30.425[0m [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:07:30.577[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:07:30.683[0m Feb 2 01:07:30.683: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-587vb" in namespace "azuredisk-5135" to be "Succeeded or Failed" Feb 2 01:07:30.788: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 104.556714ms Feb 2 01:07:32.893: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.209800679s Feb 2 01:07:34.894: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.210211454s Feb 2 01:07:36.895: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211220196s Feb 2 01:07:38.893: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.209164637s Feb 2 01:07:40.892: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.208346133s Feb 2 01:07:42.894: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210828237s Feb 2 01:07:44.892: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.208748698s Feb 2 01:07:46.897: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.213979416s Feb 2 01:07:48.899: INFO: Pod "azuredisk-volume-tester-587vb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.215186876s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:07:48.899[0m Feb 2 01:07:48.899: INFO: Pod "azuredisk-volume-tester-587vb" satisfied condition "Succeeded or Failed" Feb 2 01:07:48.899: INFO: deleting Pod "azuredisk-5135"/"azuredisk-volume-tester-587vb" Feb 2 01:07:49.003: INFO: Pod azuredisk-volume-tester-587vb has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-587vb in namespace azuredisk-5135 [38;5;243m02/02/23 01:07:49.003[0m Feb 2 01:07:49.116: INFO: deleting PVC "azuredisk-5135"/"pvc-mnx47" Feb 2 01:07:49.116: INFO: Deleting PersistentVolumeClaim "pvc-mnx47" ... skipping 159 lines ... Feb 2 01:14:28.678: INFO: PersistentVolumeClaim pvc-75cvc found and phase=Bound (4.30839614s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 01:14:28.678[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 01:14:28.781[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 01:14:28.883[0m I0202 01:14:28.883914 42332 resource_setup.go:89] adding PV (pvc-5d096896-f3cc-4af8-8507-0be3f5ad84ba) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:14:29.043[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:14:29.148[0m Feb 2 01:14:29.148: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hss8v" in namespace "azuredisk-7314" to be "Succeeded or Failed" Feb 2 01:14:29.258: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 109.941725ms Feb 2 01:14:31.368: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219480765s Feb 2 01:14:33.375: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.226483178s Feb 2 01:14:35.367: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218652288s Feb 2 01:14:37.367: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218641169s Feb 2 01:14:39.368: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.219725551s Feb 2 01:14:41.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220502955s Feb 2 01:14:43.373: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 14.224891025s Feb 2 01:14:45.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 16.220284157s Feb 2 01:14:47.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.220284725s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:14:47.369[0m Feb 2 01:14:47.369: INFO: Pod "azuredisk-volume-tester-hss8v" satisfied condition "Succeeded or Failed" Feb 2 01:14:47.369: INFO: deleting Pod "azuredisk-7314"/"azuredisk-volume-tester-hss8v" Feb 2 01:14:47.490: INFO: Pod azuredisk-volume-tester-hss8v has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hss8v in namespace azuredisk-7314 [38;5;243m02/02/23 01:14:47.49[0m Feb 2 01:14:47.608: INFO: deleting PVC "azuredisk-7314"/"pvc-75cvc" Feb 2 01:14:47.608: INFO: Deleting PersistentVolumeClaim "pvc-75cvc" ... skipping 81 lines ... Feb 2 01:14:28.678: INFO: PersistentVolumeClaim pvc-75cvc found and phase=Bound (4.30839614s) [1mSTEP:[0m checking the PVC [38;5;243m02/02/23 01:14:28.678[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/02/23 01:14:28.781[0m [1mSTEP:[0m checking the PV [38;5;243m02/02/23 01:14:28.883[0m I0202 01:14:28.883914 42332 resource_setup.go:89] adding PV (pvc-5d096896-f3cc-4af8-8507-0be3f5ad84ba) to pod () [1mSTEP:[0m deploying the pod [38;5;243m02/02/23 01:14:29.043[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/02/23 01:14:29.148[0m Feb 2 01:14:29.148: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hss8v" in namespace "azuredisk-7314" to be "Succeeded or Failed" Feb 2 01:14:29.258: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 109.941725ms Feb 2 01:14:31.368: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219480765s Feb 2 01:14:33.375: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.226483178s Feb 2 01:14:35.367: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218652288s Feb 2 01:14:37.367: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.218641169s Feb 2 01:14:39.368: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.219725551s Feb 2 01:14:41.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 12.220502955s Feb 2 01:14:43.373: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 14.224891025s Feb 2 01:14:45.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Pending", Reason="", readiness=false. Elapsed: 16.220284157s Feb 2 01:14:47.369: INFO: Pod "azuredisk-volume-tester-hss8v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.220284725s [1mSTEP:[0m Saw pod success [38;5;243m02/02/23 01:14:47.369[0m Feb 2 01:14:47.369: INFO: Pod "azuredisk-volume-tester-hss8v" satisfied condition "Succeeded or Failed" Feb 2 01:14:47.369: INFO: deleting Pod "azuredisk-7314"/"azuredisk-volume-tester-hss8v" Feb 2 01:14:47.490: INFO: Pod azuredisk-volume-tester-hss8v has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hss8v in namespace azuredisk-7314 [38;5;243m02/02/23 01:14:47.49[0m Feb 2 01:14:47.608: INFO: deleting PVC "azuredisk-7314"/"pvc-75cvc" Feb 2 01:14:47.608: INFO: Deleting PersistentVolumeClaim "pvc-75cvc" ... skipping 74 lines ...