kubernetes-sigs/azuredisk-csi-driver PR #1666 pull-azuredisk-csi-driver-e2e-capz-windows-2019-mainv2 #1616505849788764160
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] feat: fetch VMs to recover AzVolumeAttachment |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 59m18s |
| Revision | 3c9841e0e8a2720e25692fb457a0736f981f613b |
| Refs |
1666 |
... skipping 787 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 242 lines ... 1fec6b1ad547: Pull complete d3dcfcef69f5: Pull complete Digest: sha256:9b88b7e3967b6338a55be310def6e6964f723cf236b83c7f3d5d6874e215b1f7 Status: Downloaded newer image for capzci.azurecr.io/azuredisk-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 capzci.azurecr.io/azuredisk-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 not found: manifest unknown: manifest tagged by "latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' 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 1122 lines ... type: string type: object oneOf: - required: ["persistentVolumeClaimName"] - required: ["volumeSnapshotContentName"] volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 60 lines ... type: string volumeSnapshotContentName: description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable. type: string type: object volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 254 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 108 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 359 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status Required properties: detail: description: Status summarizes the current attachment state of the volume attachment Nil Status indicates that the volume has not yet been attached to the node properties: ... skipping 7 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 90 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 13 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 169 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: detail: description: Current status detail of the AzVolume Nil detail indicates that the volume has not been created properties: accessible_topology: ... skipping 28 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 154 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 34 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 831 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-feature-gates=RecoverVolumeExpansionFailure=true' - "-timeout=240s" env: - name: ADDRESS value: /csi/csi.sock volumeMounts: ... skipping 301 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:16:40.25[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:16:40.312[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:16:40.374[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:16:40.374[0m I0120 19:16:40.375240 42860 resource_setup.go:62] adding PV (pvc-cd99f454-f091-4ca1-850b-cb59470af608) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:16:40.375[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:16:40.441[0m Jan 20 19:16:40.441: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cp77w" in namespace "azuredisk-2236" to be "Succeeded or Failed" Jan 20 19:16:40.503: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 61.760026ms Jan 20 19:16:42.566: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124479847s Jan 20 19:16:44.569: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128037408s Jan 20 19:16:46.568: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126882718s Jan 20 19:16:48.567: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.125916031s Jan 20 19:16:50.568: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.127031028s ... skipping 111 lines ... Jan 20 19:20:34.570: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=true. Elapsed: 3m54.128747021s Jan 20 19:20:36.572: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.130351409s Jan 20 19:20:38.572: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.130714079s Jan 20 19:20:40.571: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.129549605s Jan 20 19:20:42.571: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4m2.129601667s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:20:42.571[0m Jan 20 19:20:42.571: INFO: Pod "azuredisk-volume-tester-cp77w" satisfied condition "Succeeded or Failed" Jan 20 19:20:42.571: INFO: deleting Pod "azuredisk-2236"/"azuredisk-volume-tester-cp77w" Jan 20 19:20:42.660: INFO: Pod azuredisk-volume-tester-cp77w has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cp77w in namespace azuredisk-2236 [38;5;243m01/20/23 19:20:42.66[0m Jan 20 19:20:42.738: INFO: deleting PVC "azuredisk-2236"/"pvc-nzmnv" Jan 20 19:20:42.738: INFO: Deleting PersistentVolumeClaim "pvc-nzmnv" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:16:40.25[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:16:40.312[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:16:40.374[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:16:40.374[0m I0120 19:16:40.375240 42860 resource_setup.go:62] adding PV (pvc-cd99f454-f091-4ca1-850b-cb59470af608) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:16:40.375[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:16:40.441[0m Jan 20 19:16:40.441: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cp77w" in namespace "azuredisk-2236" to be "Succeeded or Failed" Jan 20 19:16:40.503: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 61.760026ms Jan 20 19:16:42.566: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124479847s Jan 20 19:16:44.569: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 4.128037408s Jan 20 19:16:46.568: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126882718s Jan 20 19:16:48.567: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 8.125916031s Jan 20 19:16:50.568: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Pending", Reason="", readiness=false. Elapsed: 10.127031028s ... skipping 111 lines ... Jan 20 19:20:34.570: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=true. Elapsed: 3m54.128747021s Jan 20 19:20:36.572: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.130351409s Jan 20 19:20:38.572: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.130714079s Jan 20 19:20:40.571: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.129549605s Jan 20 19:20:42.571: INFO: Pod "azuredisk-volume-tester-cp77w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4m2.129601667s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:20:42.571[0m Jan 20 19:20:42.571: INFO: Pod "azuredisk-volume-tester-cp77w" satisfied condition "Succeeded or Failed" Jan 20 19:20:42.571: INFO: deleting Pod "azuredisk-2236"/"azuredisk-volume-tester-cp77w" Jan 20 19:20:42.660: INFO: Pod azuredisk-volume-tester-cp77w has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-cp77w in namespace azuredisk-2236 [38;5;243m01/20/23 19:20:42.66[0m Jan 20 19:20:42.738: INFO: deleting PVC "azuredisk-2236"/"pvc-nzmnv" Jan 20 19:20:42.738: INFO: Deleting PersistentVolumeClaim "pvc-nzmnv" ... skipping 37 lines ... Jan 20 19:21:26.756: INFO: PersistentVolumeClaim pvc-rmk44 found but phase is Pending instead of Bound. Jan 20 19:21:28.820: INFO: PersistentVolumeClaim pvc-rmk44 found and phase=Bound (4.191019675s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:21:28.82[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:21:28.882[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:21:28.946[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:21:28.946[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/20/23 19:21:29.012[0m Jan 20 19:21:29.012: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bmm27" in namespace "azuredisk-9837" to be "Succeeded or Failed" Jan 20 19:21:29.074: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 62.211047ms Jan 20 19:21:31.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125828784s Jan 20 19:21:33.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12602016s Jan 20 19:21:35.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125964088s Jan 20 19:21:37.139: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 8.126541742s Jan 20 19:21:39.137: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 10.125345889s ... skipping 17 lines ... Jan 20 19:22:15.142: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=true. Elapsed: 46.130053478s Jan 20 19:22:17.147: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=true. Elapsed: 48.135098325s Jan 20 19:22:19.143: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=false. Elapsed: 50.130402099s Jan 20 19:22:21.143: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=false. Elapsed: 52.130900772s Jan 20 19:22:23.142: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.129512305s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:22:23.142[0m Jan 20 19:22:23.142: INFO: Pod "azuredisk-volume-tester-bmm27" satisfied condition "Succeeded or Failed" Jan 20 19:22:23.142: INFO: deleting Pod "azuredisk-9837"/"azuredisk-volume-tester-bmm27" Jan 20 19:22:23.221: INFO: Pod azuredisk-volume-tester-bmm27 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bmm27 in namespace azuredisk-9837 [38;5;243m01/20/23 19:22:23.221[0m Jan 20 19:22:23.296: INFO: deleting PVC "azuredisk-9837"/"pvc-rmk44" Jan 20 19:22:23.296: INFO: Deleting PersistentVolumeClaim "pvc-rmk44" ... skipping 38 lines ... Jan 20 19:21:26.756: INFO: PersistentVolumeClaim pvc-rmk44 found but phase is Pending instead of Bound. Jan 20 19:21:28.820: INFO: PersistentVolumeClaim pvc-rmk44 found and phase=Bound (4.191019675s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:21:28.82[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:21:28.882[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:21:28.946[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:21:28.946[0m [1mSTEP:[0m checking that the pods command exits with no error [38;5;243m01/20/23 19:21:29.012[0m Jan 20 19:21:29.012: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bmm27" in namespace "azuredisk-9837" to be "Succeeded or Failed" Jan 20 19:21:29.074: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 62.211047ms Jan 20 19:21:31.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 2.125828784s Jan 20 19:21:33.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12602016s Jan 20 19:21:35.138: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 6.125964088s Jan 20 19:21:37.139: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 8.126541742s Jan 20 19:21:39.137: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Pending", Reason="", readiness=false. Elapsed: 10.125345889s ... skipping 17 lines ... Jan 20 19:22:15.142: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=true. Elapsed: 46.130053478s Jan 20 19:22:17.147: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=true. Elapsed: 48.135098325s Jan 20 19:22:19.143: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=false. Elapsed: 50.130402099s Jan 20 19:22:21.143: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Running", Reason="", readiness=false. Elapsed: 52.130900772s Jan 20 19:22:23.142: INFO: Pod "azuredisk-volume-tester-bmm27": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.129512305s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:22:23.142[0m Jan 20 19:22:23.142: INFO: Pod "azuredisk-volume-tester-bmm27" satisfied condition "Succeeded or Failed" Jan 20 19:22:23.142: INFO: deleting Pod "azuredisk-9837"/"azuredisk-volume-tester-bmm27" Jan 20 19:22:23.221: INFO: Pod azuredisk-volume-tester-bmm27 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bmm27 in namespace azuredisk-9837 [38;5;243m01/20/23 19:22:23.221[0m Jan 20 19:22:23.296: INFO: deleting PVC "azuredisk-9837"/"pvc-rmk44" Jan 20 19:22:23.296: INFO: Deleting PersistentVolumeClaim "pvc-rmk44" ... skipping 39 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:23:09.421[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:23:09.483[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:23:09.546[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:23:09.546[0m I0120 19:23:09.546234 42860 resource_setup.go:62] adding PV (pvc-384a6144-5a7f-44b6-8625-2bc0e6656093) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:23:09.546[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:23:09.612[0m Jan 20 19:23:09.612: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gvk9v" in namespace "azuredisk-7604" to be "Succeeded or Failed" Jan 20 19:23:09.677: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 65.213082ms Jan 20 19:23:11.740: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127967519s Jan 20 19:23:13.741: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129268085s Jan 20 19:23:15.742: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129648071s Jan 20 19:23:17.740: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.12801377s Jan 20 19:23:19.742: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.129824089s ... skipping 15 lines ... Jan 20 19:23:51.745: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=true. Elapsed: 42.132608863s Jan 20 19:23:53.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=true. Elapsed: 44.133595968s Jan 20 19:23:55.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=false. Elapsed: 46.133384833s Jan 20 19:23:57.745: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=false. Elapsed: 48.132755071s Jan 20 19:23:59.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.133660871s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:23:59.746[0m Jan 20 19:23:59.746: INFO: Pod "azuredisk-volume-tester-gvk9v" satisfied condition "Succeeded or Failed" Jan 20 19:23:59.746: INFO: deleting Pod "azuredisk-7604"/"azuredisk-volume-tester-gvk9v" Jan 20 19:23:59.824: INFO: Pod azuredisk-volume-tester-gvk9v has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-gvk9v in namespace azuredisk-7604 [38;5;243m01/20/23 19:23:59.825[0m Jan 20 19:23:59.902: INFO: deleting PVC "azuredisk-7604"/"pvc-rvxpl" Jan 20 19:23:59.902: INFO: Deleting PersistentVolumeClaim "pvc-rvxpl" ... skipping 40 lines ... [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:23:09.421[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:23:09.483[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:23:09.546[0m [1mSTEP:[0m setting up the pod [38;5;243m01/20/23 19:23:09.546[0m I0120 19:23:09.546234 42860 resource_setup.go:62] adding PV (pvc-384a6144-5a7f-44b6-8625-2bc0e6656093) to pod () [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:23:09.546[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:23:09.612[0m Jan 20 19:23:09.612: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gvk9v" in namespace "azuredisk-7604" to be "Succeeded or Failed" Jan 20 19:23:09.677: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 65.213082ms Jan 20 19:23:11.740: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 2.127967519s Jan 20 19:23:13.741: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 4.129268085s Jan 20 19:23:15.742: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 6.129648071s Jan 20 19:23:17.740: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 8.12801377s Jan 20 19:23:19.742: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Pending", Reason="", readiness=false. Elapsed: 10.129824089s ... skipping 15 lines ... Jan 20 19:23:51.745: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=true. Elapsed: 42.132608863s Jan 20 19:23:53.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=true. Elapsed: 44.133595968s Jan 20 19:23:55.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=false. Elapsed: 46.133384833s Jan 20 19:23:57.745: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Running", Reason="", readiness=false. Elapsed: 48.132755071s Jan 20 19:23:59.746: INFO: Pod "azuredisk-volume-tester-gvk9v": Phase="Succeeded", Reason="", readiness=false. Elapsed: 50.133660871s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:23:59.746[0m Jan 20 19:23:59.746: INFO: Pod "azuredisk-volume-tester-gvk9v" satisfied condition "Succeeded or Failed" Jan 20 19:23:59.746: INFO: deleting Pod "azuredisk-7604"/"azuredisk-volume-tester-gvk9v" Jan 20 19:23:59.824: INFO: Pod azuredisk-volume-tester-gvk9v has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-gvk9v in namespace azuredisk-7604 [38;5;243m01/20/23 19:23:59.825[0m Jan 20 19:23:59.902: INFO: deleting PVC "azuredisk-7604"/"pvc-rvxpl" Jan 20 19:23:59.902: INFO: Deleting PersistentVolumeClaim "pvc-rvxpl" ... skipping 38 lines ...