-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Add clusterctl upgrade test #2517
🌱 Add clusterctl upgrade test #2517
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2517 +/- ##
==========================================
+ Coverage 63.59% 63.69% +0.10%
==========================================
Files 120 120
Lines 8685 8685
==========================================
+ Hits 5523 5532 +9
+ Misses 2735 2729 -6
+ Partials 427 424 -3 ☔ View full report in Codecov by Sentry. |
2421e7a
to
a83f4c2
Compare
a83f4c2
to
917da31
Compare
/retest |
This seems to be flaky currently regarding the cluster resource set: Example:
During that 16 mins the e2e test times out. The test requires the CRS's to get deployed to get CNI and CPI running so the machines get set to Running. |
/test pull-cluster-api-provider-vsphere-e2e-main |
513bddb
to
faa6fb6
Compare
faa6fb6
to
29e6f94
Compare
2bd1148
to
6e5d1f1
Compare
/test help |
@chrischdi: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pull-cluster-api-provider-vsphere-e2e-full-main |
9fdeab9
to
4b42690
Compare
/test pull-cluster-api-provider-vsphere-e2e-full-main |
4b42690
to
ef66135
Compare
/test pull-cluster-api-provider-vsphere-e2e-full-main |
/test pull-cluster-api-provider-vsphere-e2e-full-main |
/retest |
0fa96c7
to
a5ffd1d
Compare
/retest |
/hold I think we should first get #2532 in. And afterwards bump sigs.k8s.io/cluster-api/test to a version which contains kubernetes-sigs/cluster-api#9827 Edit: updated the first reference |
test/e2e/data/infrastructure-vsphere/v1.8/cluster-template/kustomization.yaml
Outdated
Show resolved
Hide resolved
patches: | ||
- target: | ||
kind: VSphereMachineTemplate | ||
path: ../bases/remove-storage-policy.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know why we need this patch? If yes, can we add a comment here & on main?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This removes the requirement for the test to have a working storage policy, while it is part of the published yamls so it could get defined.
xref where this removal was introduced: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/1686/files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that we have a working storage policy. Should we drop this patch in a follow-up PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's learn the "why" the hard way :-)
test/e2e/data/infrastructure-vsphere/v1.8/clusterclass/kustomization.yaml
Outdated
Show resolved
Hide resolved
test/e2e/data/infrastructure-vsphere/v1.7/bases/cluster-template-topology.yaml
Outdated
Show resolved
Hide resolved
Which one? 2517 is the current PR |
Oh sorry, meant #2532 |
/test pull-cluster-api-provider-vsphere-e2e-full-main |
b0c947e
to
b64d4c3
Compare
/test pull-cluster-api-provider-vsphere-e2e-full-main |
b64d4c3
to
4a2f38e
Compare
/test pull-cluster-api-provider-vsphere-e2e-full-main |
4a2f38e
to
da8e03c
Compare
/test pull-cluster-api-provider-vsphere-e2e-full-main |
1 similar comment
/test pull-cluster-api-provider-vsphere-e2e-full-main |
patches: | ||
- target: | ||
kind: VSphereMachineTemplate | ||
path: ../bases/remove-storage-policy.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that we have a working storage policy. Should we drop this patch in a follow-up PR?
Signed-off-by: killianmuldoon <[email protected]>
5faf160
to
bc75ee1
Compare
Thank you!! /lgtm |
LGTM label has been added. Git tree hash: f86f34777a903558806d1ac27c188d1b47b4b601
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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:
Approvers can indicate their approval by writing |
/hold cancel |
/test pull-cluster-api-provider-vsphere-e2e-full-main |
Fixes #2247
TODO: