🌱 Skip kube-vip-prepare for 1.31+ k8s since CAPI won't depend on super-admin.conf

[chrischdi]

Testing kubernetes-sigs#3168

[chrischdi]

/test help

[team-cluster-api-prow]

@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-31-1-32-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-31-1-32-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-test-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main

[chrischdi]

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

[chrischdi]

Does not seem to work right away.

[team-cluster-api-prow]

@chrischdi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main	3b77f26	link	true	/test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main	3b77f26	link	true	/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main	3b77f26	link	true	/test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.