This job view page is being replaced by Spyglass soon. Check out the new job view.
PRhccheng72: [V2] fix: prevent requesting replica attachment in a row for one volume
ResultABORTED
Tests 0 failed / 0 succeeded
Started2023-01-17 17:52
Elapsed48m33s
Revisionac3d54e32c4e8daecb77c0bdd5dd97729c353957
Refs 1693

No Test Failures!


Error lines from build-log.txt

... skipping 786 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 127 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-ncw4el-kubeconfig; do sleep 1; done"
capz-ncw4el-kubeconfig                 cluster.x-k8s.io/secret   1      0s
# Get kubeconfig and store it locally.
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-ncw4el-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done"
error: the server doesn't have a resource type "nodes"
capz-ncw4el-control-plane-fwrcw   NotReady   control-plane   8s    v1.24.6
run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig ..." to work with the new target cluster
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
namespace/calico-system created
NAME             DATA   AGE
kubeadm-config   1      9s
... skipping 82 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11345  100 11345    0     0   194k      0 --:--:-- --:--:-- --:--:--  194k
Downloading https://get.helm.sh/helm-v3.10.3-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull capzci.azurecr.io/azuredisk-csi:latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc not found: manifest unknown: manifest tagged by "latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc" 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-75eecb5c876f7e33167f6048a2d9266d5626d5cc -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=75eecb5c876f7e33167f6048a2d9266d5626d5cc -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-17T18:11:58Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
ERROR: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 634 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc not found: manifest unknown: manifest tagged by "latest-v2-75eecb5c876f7e33167f6048a2d9266d5626d5cc" 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 998 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 324 lines ...
Jan 17 18:21:42.102: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sck7h] to have phase Bound
Jan 17 18:21:42.132: INFO: PersistentVolumeClaim pvc-sck7h found and phase=Bound (30.459832ms)
STEP: checking the PVC 01/17/23 18:21:42.132
STEP: validating provisioned PV 01/17/23 18:21:42.163
STEP: checking the PV 01/17/23 18:21:42.194
STEP: deploying the pod 01/17/23 18:21:42.194
STEP: checking that the pod's command exits with an error 01/17/23 18:21:42.227
Jan 17 18:21:42.227: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-scmvn" in namespace "azuredisk-3082" to be "Error status code"
Jan 17 18:21:42.259: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 32.00091ms
Jan 17 18:21:44.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064931887s
Jan 17 18:21:46.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064819288s
Jan 17 18:21:48.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065551321s
Jan 17 18:21:50.293: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066359097s
Jan 17 18:21:52.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065275142s
Jan 17 18:21:54.296: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.069681487s
Jan 17 18:21:56.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.064772203s
Jan 17 18:21:58.293: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066179481s
Jan 17 18:22:00.295: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Running", Reason="", readiness=false. Elapsed: 18.068669887s
Jan 17 18:22:02.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Failed", Reason="", readiness=false. Elapsed: 20.064845117s
STEP: Saw pod failure 01/17/23 18:22:02.292
Jan 17 18:22:02.292: INFO: Pod "azuredisk-volume-tester-scmvn" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message 01/17/23 18:22:02.292
Jan 17 18:22:02.345: INFO: deleting Pod "azuredisk-3082"/"azuredisk-volume-tester-scmvn"
Jan 17 18:22:02.386: INFO: Pod azuredisk-volume-tester-scmvn has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-scmvn in namespace azuredisk-3082 01/17/23 18:22:02.386
Jan 17 18:22:02.435: INFO: deleting PVC "azuredisk-3082"/"pvc-sck7h"
... skipping 36 lines ...
    Jan 17 18:21:42.102: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sck7h] to have phase Bound
    Jan 17 18:21:42.132: INFO: PersistentVolumeClaim pvc-sck7h found and phase=Bound (30.459832ms)
    STEP: checking the PVC 01/17/23 18:21:42.132
    STEP: validating provisioned PV 01/17/23 18:21:42.163
    STEP: checking the PV 01/17/23 18:21:42.194
    STEP: deploying the pod 01/17/23 18:21:42.194
    STEP: checking that the pod's command exits with an error 01/17/23 18:21:42.227
    Jan 17 18:21:42.227: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-scmvn" in namespace "azuredisk-3082" to be "Error status code"
    Jan 17 18:21:42.259: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 32.00091ms
    Jan 17 18:21:44.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064931887s
    Jan 17 18:21:46.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064819288s
    Jan 17 18:21:48.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065551321s
    Jan 17 18:21:50.293: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066359097s
    Jan 17 18:21:52.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065275142s
    Jan 17 18:21:54.296: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.069681487s
    Jan 17 18:21:56.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.064772203s
    Jan 17 18:21:58.293: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Pending", Reason="", readiness=false. Elapsed: 16.066179481s
    Jan 17 18:22:00.295: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Running", Reason="", readiness=false. Elapsed: 18.068669887s
    Jan 17 18:22:02.292: INFO: Pod "azuredisk-volume-tester-scmvn": Phase="Failed", Reason="", readiness=false. Elapsed: 20.064845117s
    STEP: Saw pod failure 01/17/23 18:22:02.292
    Jan 17 18:22:02.292: INFO: Pod "azuredisk-volume-tester-scmvn" satisfied condition "Error status code"
    STEP: checking that pod logs contain expected message 01/17/23 18:22:02.292
    Jan 17 18:22:02.345: INFO: deleting Pod "azuredisk-3082"/"azuredisk-volume-tester-scmvn"
    Jan 17 18:22:02.386: INFO: Pod azuredisk-volume-tester-scmvn has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

    STEP: Deleting pod azuredisk-volume-tester-scmvn in namespace azuredisk-3082 01/17/23 18:22:02.386
    Jan 17 18:22:02.435: INFO: deleting PVC "azuredisk-3082"/"pvc-sck7h"
... skipping 65 lines ...
Jan 17 18:23:06.643: INFO: PersistentVolumeClaim pvc-mhtk4 found and phase=Bound (30.844733ms)
STEP: checking the PVC 01/17/23 18:23:06.643
STEP: validating provisioned PV 01/17/23 18:23:06.674
STEP: checking the PV 01/17/23 18:23:06.706
STEP: attaching disk to node#0 01/17/23 18:23:06.753
STEP: deploying the pod 01/17/23 18:23:19.088
STEP: checking that the pod's command exits with no error 01/17/23 18:23:19.121
Jan 17 18:23:19.121: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5nzd8" in namespace "azuredisk-6590" to be "Succeeded or Failed"
Jan 17 18:23:19.153: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.276434ms
Jan 17 18:23:21.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064712846s
Jan 17 18:23:23.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064138406s
Jan 17 18:23:25.185: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063256473s
Jan 17 18:23:27.185: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063386261s
Jan 17 18:23:29.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064284117s
... skipping 5 lines ...
Jan 17 18:23:41.187: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 22.06567132s
Jan 17 18:23:43.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 24.064731635s
Jan 17 18:23:45.188: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 26.066690808s
Jan 17 18:23:47.187: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.065534179s
Jan 17 18:23:49.189: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.067419889s
STEP: Saw pod success 01/17/23 18:23:49.189
Jan 17 18:23:49.189: INFO: Pod "azuredisk-volume-tester-5nzd8" satisfied condition "Succeeded or Failed"
Jan 17 18:23:49.189: INFO: deleting Pod "azuredisk-6590"/"azuredisk-volume-tester-5nzd8"
Jan 17 18:23:49.236: INFO: Pod azuredisk-volume-tester-5nzd8 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-5nzd8 in namespace azuredisk-6590 01/17/23 18:23:49.236
Jan 17 18:23:49.353: INFO: deleting PVC "azuredisk-6590"/"pvc-mhtk4"
Jan 17 18:23:49.353: INFO: Deleting PersistentVolumeClaim "pvc-mhtk4"
... skipping 36 lines ...
    Jan 17 18:23:06.643: INFO: PersistentVolumeClaim pvc-mhtk4 found and phase=Bound (30.844733ms)
    STEP: checking the PVC 01/17/23 18:23:06.643
    STEP: validating provisioned PV 01/17/23 18:23:06.674
    STEP: checking the PV 01/17/23 18:23:06.706
    STEP: attaching disk to node#0 01/17/23 18:23:06.753
    STEP: deploying the pod 01/17/23 18:23:19.088
    STEP: checking that the pod's command exits with no error 01/17/23 18:23:19.121
    Jan 17 18:23:19.121: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5nzd8" in namespace "azuredisk-6590" to be "Succeeded or Failed"
    Jan 17 18:23:19.153: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.276434ms
    Jan 17 18:23:21.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064712846s
    Jan 17 18:23:23.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.064138406s
    Jan 17 18:23:25.185: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063256473s
    Jan 17 18:23:27.185: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.063386261s
    Jan 17 18:23:29.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.064284117s
... skipping 5 lines ...
    Jan 17 18:23:41.187: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 22.06567132s
    Jan 17 18:23:43.186: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 24.064731635s
    Jan 17 18:23:45.188: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 26.066690808s
    Jan 17 18:23:47.187: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Pending", Reason="", readiness=false. Elapsed: 28.065534179s
    Jan 17 18:23:49.189: INFO: Pod "azuredisk-volume-tester-5nzd8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.067419889s
    STEP: Saw pod success 01/17/23 18:23:49.189
    Jan 17 18:23:49.189: INFO: Pod "azuredisk-volume-tester-5nzd8" satisfied condition "Succeeded or Failed"
    Jan 17 18:23:49.189: INFO: deleting Pod "azuredisk-6590"/"azuredisk-volume-tester-5nzd8"
    Jan 17 18:23:49.236: INFO: Pod azuredisk-volume-tester-5nzd8 has the following logs: hello world

    STEP: Deleting pod azuredisk-volume-tester-5nzd8 in namespace azuredisk-6590 01/17/23 18:23:49.236
    Jan 17 18:23:49.353: INFO: deleting PVC "azuredisk-6590"/"pvc-mhtk4"
    Jan 17 18:23:49.353: INFO: Deleting PersistentVolumeClaim "pvc-mhtk4"
... skipping 281 lines ...