🌱 Add ClusterClass topology tests for ubuntu and bastion - #3121
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @larainema. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
|
/test pull-cluster-api-provider-openstack-e2e-full-test |
|
@larainema: The following test failed, say
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. DetailsInstructions 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. |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
15dd111 to
78d63fe
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/remove-lifecycle stale |
|
/test pull-cluster-api-provider-openstack-e2e-full-test |
|
There is some issue with this. |
Add two new non-PR-blocking ClusterClass test variants: - topology-ubuntu: Tests ClusterClass with a standard ubuntu image without ignition/sysext configuration - topology-bastion: Tests ClusterClass with a standard ubuntu image and bastion enabled These tests exercise additional ClusterClass configurations beyond the existing flatcar+sysext PR-blocking test, verifying that the ClusterClass works correctly with different variable combinations. The tests are not tagged as PR-Blocking so they only run in the full periodic test suite.
78d63fe to
2eb6968
Compare
|
Thanks, good catch! Fixed in the latest push by matching the existing topology templates and using /test pull-cluster-api-provider-openstack-e2e-full-test |
|
I checked the latest full e2e failure. The original admission-webhook error is gone, and both new specs passed in that run:
The Ginkgo suite itself ended with So I do not see another template/test failure from this PR in that run; this looks like a CI cleanup/infra flake. Rerunning the optional job: /test pull-cluster-api-provider-openstack-e2e-full-test |
What issue does this PR address?
Issue #2796
What does this PR do?
Adds two new non-PR-blocking ClusterClass test variants to the e2e test suite:
injectIgnitionSysext: false)bastion.enabled: true)These complement the existing
[PR-Blocking]topology test (which uses flatcar + ignition/sysext) by exercising additional variable combinations of thedev-testClusterClass.Changes
topology-ubuntu/andtopology-bastion/clusterclass_test.gowith twoQuickStartSpectests tagged[ClusterClass]only (not[PR-Blocking])FlavorTopologyUbuntuandFlavorTopologyBastionMakefileande2e_conf.yamlto register the new templatesWhy not PR-blocking?
As noted in the issue, these tests should run in the periodic/full suite only to avoid adding to PR verification time. They are tagged with
[ClusterClass]but intentionally omit the[PR-Blocking]tag.