kubernetes-sigs/azuredisk-csi-driver PR #1532 pull-azuredisk-csi-driver-e2e-migration-mainv2 #1633606763997564928
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | sunpa93: [V2] bug: WaitForAttach call should also be able to detach replicas for primary |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 36m58s |
| Revision | 1dd1af31de5248ca06be68661f60660f88473c29 |
| Refs |
1532 |
... skipping 107 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 187k 0 --:--:-- --:--:-- --:--:-- 187k Downloading https://get.helm.sh/helm-v3.11.2-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm docker pull k8sprow.azurecr.io/azuredisk-csi:latest-v2-14b0583090e9a831511c8f950af0dabfa852579b || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-14b0583090e9a831511c8f950af0dabfa852579b not found: manifest unknown: manifest tagged by "latest-v2-14b0583090e9a831511c8f950af0dabfa852579b" 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-14b0583090e9a831511c8f950af0dabfa852579b -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=14b0583090e9a831511c8f950af0dabfa852579b -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-03-08T23:20:46Z -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 721 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-14b0583090e9a831511c8f950af0dabfa852579b || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-14b0583090e9a831511c8f950af0dabfa852579b not found: manifest unknown: manifest tagged by "latest-v2-14b0583090e9a831511c8f950af0dabfa852579b" 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 1046 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 282 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:17.391[0m Mar 8 23:31:17.391: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:17.392[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:17.592[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:17.647[0m I0308 23:31:17.702528 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.207: INFO: Unexpected error: <*errors.errorString | 0xc00012af50>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.207: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-8235" for this suite. [38;5;243m03/08/23 23:31:18.207[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:17.391[0m Mar 8 23:31:17.391: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:17.392[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:17.592[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:17.647[0m I0308 23:31:17.702528 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.207: INFO: Unexpected error: <*errors.errorString | 0xc00012af50>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.207: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-8235" for this suite. [38;5;243m03/08/23 23:31:18.207[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:18.207: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould succeed when creating a PremiumV2_LRS disk [disk.csi.azure.com][windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:161[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.238[0m Mar 8 23:31:18.238: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.24[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.324[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.38[0m I0308 23:31:18.435560 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.505: INFO: Unexpected error: <*errors.errorString | 0xc00059bbd0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.505: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-8222" for this suite. [38;5;243m03/08/23 23:31:18.506[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.238[0m Mar 8 23:31:18.238: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.24[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.324[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.38[0m I0308 23:31:18.435560 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.505: INFO: Unexpected error: <*errors.errorString | 0xc00059bbd0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.505: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-8222" for this suite. [38;5;243m03/08/23 23:31:18.506[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:18.505: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould succeed when reattaching a disk to a new node on DanglingAttachError [disk.csi.azure.com][csi-azuredisk-scheduler-extender][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:180[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.541[0m Mar 8 23:31:18.541: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.543[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.631[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.687[0m I0308 23:31:18.744699 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.817: INFO: Unexpected error: <*errors.errorString | 0xc0005351d0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.817: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-2634" for this suite. [38;5;243m03/08/23 23:31:18.818[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.541[0m Mar 8 23:31:18.541: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.543[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.631[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.687[0m I0308 23:31:18.744699 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:18.817: INFO: Unexpected error: <*errors.errorString | 0xc0005351d0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:18.817: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-2634" for this suite. [38;5;243m03/08/23 23:31:18.818[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:18.817: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould use a pre-provisioned volume and retain PV with reclaimPolicy "Retain" [disk.csi.azure.com][windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:223[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.848[0m Mar 8 23:31:18.848: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.851[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.936[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.992[0m I0308 23:31:19.048478 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.119: INFO: Unexpected error: <*errors.errorString | 0xc000535ed0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.120: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4907" for this suite. [38;5;243m03/08/23 23:31:19.12[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:18.848[0m Mar 8 23:31:18.848: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:18.851[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:18.936[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:18.992[0m I0308 23:31:19.048478 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.119: INFO: Unexpected error: <*errors.errorString | 0xc000535ed0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.120: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4907" for this suite. [38;5;243m03/08/23 23:31:19.12[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:19.120: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould succeed when creating a shared disk [disk.csi.azure.com][windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:255[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.151[0m Mar 8 23:31:19.151: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.155[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.251[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.308[0m I0308 23:31:19.365745 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.438: INFO: Unexpected error: <*errors.errorString | 0xc00050d8f0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.438: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4966" for this suite. [38;5;243m03/08/23 23:31:19.439[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.151[0m Mar 8 23:31:19.151: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.155[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.251[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.308[0m I0308 23:31:19.365745 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.438: INFO: Unexpected error: <*errors.errorString | 0xc00050d8f0>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.438: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4966" for this suite. [38;5;243m03/08/23 23:31:19.439[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:19.438: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:273[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.468[0m Mar 8 23:31:19.468: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.47[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.555[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.613[0m I0308 23:31:19.669296 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.740: INFO: Unexpected error: <*errors.errorString | 0xc000dbb040>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.740: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-6316" for this suite. [38;5;243m03/08/23 23:31:19.741[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.468[0m Mar 8 23:31:19.468: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.47[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.555[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.613[0m I0308 23:31:19.669296 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:19.740: INFO: Unexpected error: <*errors.errorString | 0xc000dbb040>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:19.740: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-6316" for this suite. [38;5;243m03/08/23 23:31:19.741[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:19.740: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould succeed when creating a single pod and with replica attachments [disk.csi.azure.com][csi-azuredisk-scheduler-extender][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:341[0m [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.771[0m Mar 8 23:31:19.771: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.773[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.856[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.911[0m I0308 23:31:19.965577 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:20.035: INFO: Unexpected error: <*errors.errorString | 0xc000539f20>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:20.036: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4444" for this suite. [38;5;243m03/08/23 23:31:20.036[0m [38;5;243m------------------------------[0m ... skipping 9 lines ... [1mSTEP:[0m Creating a kubernetes client [38;5;243m03/08/23 23:31:19.771[0m Mar 8 23:31:19.771: INFO: >>> kubeConfig: /root/tmp3059114288/kubeconfig/kubeconfig.centralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m03/08/23 23:31:19.773[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:19.856[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:19.911[0m I0308 23:31:19.965577 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk Mar 8 23:31:20.035: INFO: Unexpected error: <*errors.errorString | 0xc000539f20>: { s: "could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)", } Mar 8 23:31:20.036: FAIL: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+) Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/e2e.glob..func4.2() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:96 +0xb8 [1mSTEP:[0m Destroying namespace "azuredisk-4444" for this suite. [38;5;243m03/08/23 23:31:20.036[0m [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for CSI drivers[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:32[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mMar 8 23:31:20.036: could not get disk name from , correct format: (?i).*/subscriptions/(?:.*)/resourceGroups/(?:.*)/providers/Microsoft.Compute/disks/(.+)[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:96[0m [38;5;243m------------------------------[0m [0mPre-Provisioned [38;5;243m[single-az][0m [1mshould create an inline volume by in-tree driver [kubernetes.io/azure-disk][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:397[0m ... skipping 3 lines ... [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:20.15[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:20.205[0m I0308 23:31:20.259369 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk [1mSTEP:[0m Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-bj6fa9uy/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume" [38;5;243m03/08/23 23:31:22.882[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:31:22.882[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:31:22.912[0m Mar 8 23:31:22.913: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hvqsh" in namespace "azuredisk-6920" to be "Succeeded or Failed" Mar 8 23:31:22.943: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.329437ms Mar 8 23:31:24.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.05904018s Mar 8 23:31:26.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.058959684s Mar 8 23:31:28.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.059793154s Mar 8 23:31:30.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.060070379s Mar 8 23:31:32.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.0590511s Mar 8 23:31:34.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.059107477s Mar 8 23:31:36.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.059061134s Mar 8 23:31:38.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.059544256s Mar 8 23:31:40.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.060644673s Mar 8 23:31:42.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.060629301s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:31:42.973[0m Mar 8 23:31:42.974: INFO: Pod "azuredisk-volume-tester-hvqsh" satisfied condition "Succeeded or Failed" Mar 8 23:31:42.974: INFO: deleting Pod "azuredisk-6920"/"azuredisk-volume-tester-hvqsh" Mar 8 23:31:43.023: INFO: Pod azuredisk-volume-tester-hvqsh has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hvqsh in namespace azuredisk-6920 [38;5;243m03/08/23 23:31:43.023[0m [1mSTEP:[0m Destroying namespace "azuredisk-6920" for this suite. [38;5;243m03/08/23 23:31:43.058[0m [38;5;243m------------------------------[0m ... skipping 12 lines ... [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m03/08/23 23:31:20.15[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m03/08/23 23:31:20.205[0m I0308 23:31:20.259369 17769 azuredisk_driver.go:52] Using azure disk driver: kubernetes.io/azure-disk [1mSTEP:[0m Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-bj6fa9uy/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume" [38;5;243m03/08/23 23:31:22.882[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:31:22.882[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:31:22.912[0m Mar 8 23:31:22.913: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hvqsh" in namespace "azuredisk-6920" to be "Succeeded or Failed" Mar 8 23:31:22.943: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 30.329437ms Mar 8 23:31:24.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.05904018s Mar 8 23:31:26.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.058959684s Mar 8 23:31:28.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.059793154s Mar 8 23:31:30.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.060070379s Mar 8 23:31:32.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.0590511s Mar 8 23:31:34.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 12.059107477s Mar 8 23:31:36.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 14.059061134s Mar 8 23:31:38.972: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 16.059544256s Mar 8 23:31:40.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Pending", Reason="", readiness=false. Elapsed: 18.060644673s Mar 8 23:31:42.973: INFO: Pod "azuredisk-volume-tester-hvqsh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.060629301s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:31:42.973[0m Mar 8 23:31:42.974: INFO: Pod "azuredisk-volume-tester-hvqsh" satisfied condition "Succeeded or Failed" Mar 8 23:31:42.974: INFO: deleting Pod "azuredisk-6920"/"azuredisk-volume-tester-hvqsh" Mar 8 23:31:43.023: INFO: Pod azuredisk-volume-tester-hvqsh has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-hvqsh in namespace azuredisk-6920 [38;5;243m03/08/23 23:31:43.023[0m [1mSTEP:[0m Destroying namespace "azuredisk-6920" for this suite. [38;5;243m03/08/23 23:31:43.058[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 240 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/08/23 23:31:45.181[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/08/23 23:31:45.181[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:31:45.21[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:31:45.21[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:31:45.24[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:31:45.24[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:31:45.269[0m Mar 8 23:31:45.269: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-sh9ft" in namespace "azuredisk-4773" to be "Succeeded or Failed" Mar 8 23:31:45.302: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 33.543971ms Mar 8 23:31:47.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063138304s Mar 8 23:31:49.330: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.061559044s Mar 8 23:31:51.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.062596278s Mar 8 23:31:53.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.062249671s Mar 8 23:31:55.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062427211s ... skipping 2 lines ... Mar 8 23:32:01.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 16.062300364s Mar 8 23:32:03.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 18.062252991s Mar 8 23:32:05.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 20.061807003s Mar 8 23:32:07.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 22.063037815s Mar 8 23:32:09.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.062934591s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:32:09.332[0m Mar 8 23:32:09.332: INFO: Pod "azuredisk-volume-tester-sh9ft" satisfied condition "Succeeded or Failed" Mar 8 23:32:09.332: INFO: deleting Pod "azuredisk-4773"/"azuredisk-volume-tester-sh9ft" Mar 8 23:32:09.387: INFO: Pod azuredisk-volume-tester-sh9ft has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-sh9ft in namespace azuredisk-4773 [38;5;243m03/08/23 23:32:09.387[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:32:09.449[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:32:09.477[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/08/23 23:31:45.181[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/08/23 23:31:45.181[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:31:45.21[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:31:45.21[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:31:45.24[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:31:45.24[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:31:45.269[0m Mar 8 23:31:45.269: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-sh9ft" in namespace "azuredisk-4773" to be "Succeeded or Failed" Mar 8 23:31:45.302: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 33.543971ms Mar 8 23:31:47.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063138304s Mar 8 23:31:49.330: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 4.061559044s Mar 8 23:31:51.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 6.062596278s Mar 8 23:31:53.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 8.062249671s Mar 8 23:31:55.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 10.062427211s ... skipping 2 lines ... Mar 8 23:32:01.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 16.062300364s Mar 8 23:32:03.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 18.062252991s Mar 8 23:32:05.331: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 20.061807003s Mar 8 23:32:07.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Pending", Reason="", readiness=false. Elapsed: 22.063037815s Mar 8 23:32:09.332: INFO: Pod "azuredisk-volume-tester-sh9ft": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.062934591s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:32:09.332[0m Mar 8 23:32:09.332: INFO: Pod "azuredisk-volume-tester-sh9ft" satisfied condition "Succeeded or Failed" Mar 8 23:32:09.332: INFO: deleting Pod "azuredisk-4773"/"azuredisk-volume-tester-sh9ft" Mar 8 23:32:09.387: INFO: Pod azuredisk-volume-tester-sh9ft has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-sh9ft in namespace azuredisk-4773 [38;5;243m03/08/23 23:32:09.387[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:32:09.449[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:32:09.477[0m ... skipping 142 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:32:52.053[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:32:52.054[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:32:52.083[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:32:52.083[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m03/08/23 23:32:52.111[0m Mar 8 23:33:10.168: INFO: deleting Pod "azuredisk-6371"/"azuredisk-volume-tester-dnmkw" Mar 8 23:33:10.198: INFO: Error getting logs for pod azuredisk-volume-tester-dnmkw: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-dnmkw) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-dnmkw in namespace azuredisk-6371 [38;5;243m03/08/23 23:33:10.198[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:33:10.257[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:33:10.284[0m Mar 8 23:33:10.285: INFO: deleting PVC "azuredisk-6371"/"pvc-782qg" Mar 8 23:33:10.285: INFO: Deleting PersistentVolumeClaim "pvc-782qg" [1mSTEP:[0m waiting for claim's PV "pvc-d14ce0f2-da0d-41c0-8cc5-d8ce4e7dbd4b" to be deleted [38;5;243m03/08/23 23:33:10.313[0m ... skipping 53 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:32:52.053[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:32:52.054[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:32:52.083[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:32:52.083[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m03/08/23 23:32:52.111[0m Mar 8 23:33:10.168: INFO: deleting Pod "azuredisk-6371"/"azuredisk-volume-tester-dnmkw" Mar 8 23:33:10.198: INFO: Error getting logs for pod azuredisk-volume-tester-dnmkw: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-dnmkw) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-dnmkw in namespace azuredisk-6371 [38;5;243m03/08/23 23:33:10.198[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:33:10.257[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:33:10.284[0m Mar 8 23:33:10.285: INFO: deleting PVC "azuredisk-6371"/"pvc-782qg" Mar 8 23:33:10.285: INFO: Deleting PersistentVolumeClaim "pvc-782qg" [1mSTEP:[0m waiting for claim's PV "pvc-d14ce0f2-da0d-41c0-8cc5-d8ce4e7dbd4b" to be deleted [38;5;243m03/08/23 23:33:10.313[0m ... skipping 50 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/08/23 23:35:36.869[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/08/23 23:35:36.869[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:35:36.898[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:35:36.898[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:35:36.927[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:35:36.928[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:35:36.963[0m Mar 8 23:35:36.964: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qf74c" in namespace "azuredisk-2" to be "Succeeded or Failed" Mar 8 23:35:36.992: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 27.784332ms Mar 8 23:35:39.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057127175s Mar 8 23:35:41.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.057218959s Mar 8 23:35:43.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.056562351s Mar 8 23:35:45.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.056922743s Mar 8 23:35:47.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.056520939s Mar 8 23:35:49.022: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.058450991s Mar 8 23:35:51.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.056881463s Mar 8 23:35:53.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.057005087s Mar 8 23:35:55.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.056500033s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:35:55.02[0m Mar 8 23:35:55.020: INFO: Pod "azuredisk-volume-tester-qf74c" satisfied condition "Succeeded or Failed" Mar 8 23:35:55.020: INFO: deleting Pod "azuredisk-2"/"azuredisk-volume-tester-qf74c" Mar 8 23:35:55.075: INFO: Pod azuredisk-volume-tester-qf74c has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qf74c in namespace azuredisk-2 [38;5;243m03/08/23 23:35:55.075[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:35:55.137[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:35:55.165[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/08/23 23:35:36.869[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/08/23 23:35:36.869[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:35:36.898[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:35:36.898[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:35:36.927[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:35:36.928[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m03/08/23 23:35:36.963[0m Mar 8 23:35:36.964: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qf74c" in namespace "azuredisk-2" to be "Succeeded or Failed" Mar 8 23:35:36.992: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 27.784332ms Mar 8 23:35:39.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057127175s Mar 8 23:35:41.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 4.057218959s Mar 8 23:35:43.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 6.056562351s Mar 8 23:35:45.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 8.056922743s Mar 8 23:35:47.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 10.056520939s Mar 8 23:35:49.022: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 12.058450991s Mar 8 23:35:51.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 14.056881463s Mar 8 23:35:53.021: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Pending", Reason="", readiness=false. Elapsed: 16.057005087s Mar 8 23:35:55.020: INFO: Pod "azuredisk-volume-tester-qf74c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.056500033s [1mSTEP:[0m Saw pod success [38;5;243m03/08/23 23:35:55.02[0m Mar 8 23:35:55.020: INFO: Pod "azuredisk-volume-tester-qf74c" satisfied condition "Succeeded or Failed" Mar 8 23:35:55.020: INFO: deleting Pod "azuredisk-2"/"azuredisk-volume-tester-qf74c" Mar 8 23:35:55.075: INFO: Pod azuredisk-volume-tester-qf74c has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-qf74c in namespace azuredisk-2 [38;5;243m03/08/23 23:35:55.075[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:35:55.137[0m [1mSTEP:[0m checking the PV [38;5;243m03/08/23 23:35:55.165[0m ... skipping 104 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m03/08/23 23:36:37.173[0m [1mSTEP:[0m creating a StorageClass [38;5;243m03/08/23 23:36:37.173[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m03/08/23 23:36:37.202[0m [1mSTEP:[0m creating a PVC [38;5;243m03/08/23 23:36:37.202[0m [1mSTEP:[0m setting up the pod [38;5;243m03/08/23 23:36:37.232[0m [1mSTEP:[0m deploying the pod [38;5;243m03/08/23 23:36:37.232[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m03/08/23 23:36:37.261[0m Mar 8 23:36:37.261: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-8cc2t" in namespace "azuredisk-6895" to be "Error status code" Mar 8 23:36:37.289: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 27.491156ms Mar 8 23:36:39.317: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055792934s Mar 8 23:36:41.317: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 4.056090932s Mar 8 23:36:43.318: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 6.0567475s Mar 8 23:36:45.319: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 8.058328264s Mar 8 23:36:47.317: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 10.056425184s Mar 8 23:36:49.318: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 12.057118951s Mar 8 23:36:51.317: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 14.05635018s Mar 8 23:36:53.318: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 16.056459057s Mar 8 23:36:55.319: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 18.057637341s Mar 8 23:36:57.318: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Pending", Reason="", readiness=false. Elapsed: 20.057098458s Mar 8 23:36:59.317: INFO: Pod "azuredisk-volume-tester-8cc2t": Phase="Failed", Reason="", readiness=false. Elapsed: 22.056152209s [1mSTEP:[0m Saw pod failure [38;5;243m03/08/23 23:36:59.317[0m Mar 8 23:36:59.317: INFO: Pod "azuredisk-volume-tester-8cc2t" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m03/08/23 23:36:59.317[0m Mar 8 23:36:59.349: INFO: deleting Pod "azuredisk-6895"/"azuredisk-volume-tester-8cc2t" Mar 8 23:36:59.378: INFO: Pod azuredisk-volume-tester-8cc2t has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-8cc2t in namespace azuredisk-6895 [38;5;243m03/08/23 23:36:59.378[0m [1mSTEP:[0m validating provisioned PV [38;5;243m03/08/23 23:36:59.439[0m ... skipping 4 lines ... Mar 8 23:36:59.496: INFO: Waiting up to 10m0s for PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d to get deleted Mar 8 23:36:59.524: INFO: PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d found and phase=Released (27.665776ms) Mar 8 23:37:04.556: INFO: PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d found and phase=Released (5.05978237s) Mar 8 23:37:09.587: INFO: PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d found and phase=Released (10.090180803s) Mar 8 23:37:14.619: INFO: PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d found and phase=Released (15.12220907s) Mar 8 23:37:19.648: INFO: PersistentVolume pvc-9dcb1cca-d4a8-44ae-b503-3a425343504d found and phase=Released (20.151818945s) {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2023-03-08T23:37:22Z"} ++ early_exit_handler ++ '[' -n 185 ']' ++ kill -TERM 185 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...