🌱 test: implement check for all pods running

[chrischdi]

What this PR does / why we need it:

Adds a check to the basic PR-Blocking test to check if all pods (e.g. CSI) are running.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[chrischdi]

/test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main

[chrischdi]

How it looks like when it fails:

Expected success, but got an error:
    <errors.aggregate | len:3, cap:4>: 
    [pod vmware-system-csi/vsphere-csi-controller-854645997c-krshf not ready: reason="ContainersNotReady" message="containers with unready status: [vsphere-csi-controller vsphere-syncer]", pod vmware-system-csi/vsphere-csi-node-dhmgw not ready: reason="ContainersNotReady" message="containers with unready status: [node-driver-registrar]", pod vmware-system-csi/vsphere-csi-node-n46ml not ready: reason="ContainersNotReady" message="containers with unready status: [node-driver-registrar]"]
    [
        <*errors.errorString | 0xc0013a1460>{
            s: "pod vmware-system-csi/vsphere-csi-controller-854645997c-krshf not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [vsphere-csi-controller vsphere-syncer]\"",
        },
        <*errors.errorString | 0xc0013a1500>{
            s: "pod vmware-system-csi/vsphere-csi-node-dhmgw not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [node-driver-registrar]\"",
        },
        <*errors.errorString | 0xc0013a1540>{
            s: "pod vmware-system-csi/vsphere-csi-node-n46ml not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [node-driver-registrar]\"",
        },
    ] failed [FAILED] Timed out after 300.000s.
Expected success, but got an error:
    <errors.aggregate | len:3, cap:4>: 
    [pod vmware-system-csi/vsphere-csi-controller-854645997c-krshf not ready: reason="ContainersNotReady" message="containers with unready status: [vsphere-csi-controller vsphere-syncer]", pod vmware-system-csi/vsphere-csi-node-dhmgw not ready: reason="ContainersNotReady" message="containers with unready status: [node-driver-registrar]", pod vmware-system-csi/vsphere-csi-node-n46ml not ready: reason="ContainersNotReady" message="containers with unready status: [node-driver-registrar]"]
    [
        <*errors.errorString | 0xc0013a1460>{
            s: "pod vmware-system-csi/vsphere-csi-controller-854645997c-krshf not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [vsphere-csi-controller vsphere-syncer]\"",
        },
        <*errors.errorString | 0xc0013a1500>{
            s: "pod vmware-system-csi/vsphere-csi-node-dhmgw not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [node-driver-registrar]\"",
        },
        <*errors.errorString | 0xc0013a1540>{
            s: "pod vmware-system-csi/vsphere-csi-node-n46ml not ready: reason=\"ContainersNotReady\" message=\"containers with unready status: [node-driver-registrar]\"",
        },
    ]

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-vsphere/3089/pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main/1808799328001593344

[chrischdi]

/test help

[k8s-ci-robot]

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-30-1-31-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-30-1-31-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main
• /test pull-cluster-api-provider-vsphere-test-main
• /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-vsphere-apidiff-main
• /test pull-cluster-api-provider-vsphere-janitor-main

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-vsphere-apidiff-main
• pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• pull-cluster-api-provider-vsphere-test-main
• pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[chrischdi]

/test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
/test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main

[sbueringer]

Thank you very much!

Also for showing an example

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: dc281a0715f800b8196854c0e95e6ceaee21ab51

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment