Add CAPO verify tests

[mdbooth]

TODO before merging:

• Merge CARRY: Fix vendoring cluster-api-provider-openstack#265
• Backport and merge 🌱 Build setup-envtest in hack/tools kubernetes-sigs/cluster-api-provider-openstack#1707
• Backport and merge 🌱 Ignore vendor directories in boilerplate check kubernetes-sigs/cluster-api-provider-openstack#1709

[mdbooth]

We expect verify to fail until we merge:

• 🌱 Ignore vendor directories in boilerplate check kubernetes-sigs/cluster-api-provider-openstack#1709
• CARRY: Fix vendoring cluster-api-provider-openstack#265

I'll run it anyway just to confirm it runs the make target before failing.

/pj-rehearse

[mdbooth]

Failed because golangci-lint is trying to write to /.cache, which is unexpected. Added an explicit cache directory and trying again until it fails for the expected reasons.

/pj-rehearse

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@mdbooth: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-cluster-api-provider-openstack-main-verify	openshift/cluster-api-provider-openstack	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[mdbooth]

This is now failing because vendoring is broken on the main branch, which is expected.

/pj-rehearse skip

[mdbooth]

/assign @mandre

[EmilienM]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM, mdbooth

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-api-provider-openstack/OWNERS [EmilienM,mdbooth]
• ci-operator/jobs/openshift/cluster-api-provider-openstack/OWNERS [EmilienM,mdbooth]

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

[mdbooth]

/hold

[mdbooth]

As pointed out by @EmilienM the test and verify jobs are required, which is preventing us from merging anything in CAPO. Making this new test pass requires merging and backporting an additional upstream PR.

Therefore we MUST NOT merge this until we have merged:

• CARRY: Fix vendoring cluster-api-provider-openstack#265

and backported and merged:

• 🌱 Build setup-envtest in hack/tools kubernetes-sigs/cluster-api-provider-openstack#1707
• 🌱 Ignore vendor directories in boilerplate check kubernetes-sigs/cluster-api-provider-openstack#1709

[openshift-ci]

@mdbooth: 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
ci/rehearse/openshift/cluster-api-provider-openstack/main/verify	9a11991	link	unknown	/pj-rehearse pull-ci-openshift-cluster-api-provider-openstack-main-verify

Full PR test history. Your PR dashboard.

Details

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

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-merge-robot]

PR needs rebase.

Details

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.

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.