🌱 Print conformance image used in kubetest

[sbueringer]

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
This PR helps to figure out via logs which version of the conformance tests were executed

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 #

[sbueringer]

/test ?

[k8s-ci-robot]

@sbueringer: The following commands are available to trigger required jobs:

• /test pull-cluster-api-build-main
• /test pull-cluster-api-e2e-blocking-main
• /test pull-cluster-api-e2e-conformance-ci-latest-main
• /test pull-cluster-api-e2e-conformance-main
• /test pull-cluster-api-e2e-dualstack-and-ipv6-main
• /test pull-cluster-api-e2e-main
• /test pull-cluster-api-e2e-mink8s-main
• /test pull-cluster-api-e2e-upgrade-1-29-1-30-main
• /test pull-cluster-api-test-main
• /test pull-cluster-api-test-mink8s-main
• /test pull-cluster-api-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-apidiff-main

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

• pull-cluster-api-apidiff-main
• pull-cluster-api-build-main
• pull-cluster-api-e2e-blocking-main
• pull-cluster-api-test-main
• pull-cluster-api-verify-main

In response to this:

/test ?

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/test-infra repository.

[sbueringer]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main

[chrischdi]

/lgtm
/approve

/hold to check the output of pull-cluster-api-e2e-conformance-ci-latest-main

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 10bfd5393e09ad4d5179fc735b31a7fa88fa3d5c

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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 [chrischdi]

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

[sbueringer]

Should be fine

STEP: Running e2e test: dir=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e, command=["-slowSpecThreshold=120" "-nodes=5" "/usr/local/bin/e2e.test" "--" "--report-prefix=kubetest." "--num-nodes=5" "--kubeconfig=/tmp/kubeconfig" "--provider=skeleton" "--report-dir=/output" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "-system-pods-startup-timeout=5m" "-ginkgo.flakeAttempts=3" "-ginkgo.focus=\[Conformance\]" "-ginkgo.skip=\[Serial\]" "-ginkgo.trace=true" "-disable-log-dump=true" "-ginkgo.progress=true" "-ginkgo.slowSpecThreshold=120" "-ginkgo.v=true"], image="registry.k8s.io/conformance:v1.29.0" @ 01/30/24 14:53:47.633

[chrischdi]

/hold cancel

[chrischdi]

/area testing

[sbueringer]

(print works but I have to fix the test to actually test 1.30 latest)

[sbueringer]

/cherry-pick release-1.6

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #10081

In response to this:

/cherry-pick release-1.6

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/test-infra repository.