Trying to debug why clusters aren't coming up for PR jobs

[marosset]

No description provided.

[marosset]

/test pull-e2e-capz-windows-2022-extension-community

[marosset]

/retest

[marosset]

/retest

[k8s-ci-robot]

@marosset: The following test 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-e2e-capz-windows-2022-extension-community	db8a4b6	link	false	/test pull-e2e-capz-windows-2022-extension-community

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[marosset]

/test pull-e2e-capz-windows-2022-extension

[jsturtevant]

pull-e2e-capz-windows-2022-extension-community is a work in progress, and is expected to fail. we can make it so it doesn't run on all jobs untill we are ready

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsturtevant, marosset

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 [jsturtevant,marosset]

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