-
Notifications
You must be signed in to change notification settings - Fork 430
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
optional flatcar tests will create a loadbalancer #3386
optional flatcar tests will create a loadbalancer #3386
Conversation
/test ls |
@nawazkh: 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. |
This comment was marked as outdated.
This comment was marked as outdated.
a2435bd
to
954678d
Compare
/test pull-cluster-api-provider-azure-e2e-optional |
Hmm, as expected.
|
I've created #3387 to track the investigation, as we will need both test and a fix for this. I can reproduce it on my cluster, so I'm investigating, will share findings in the issue. |
test/e2e/azure_test.go
Outdated
@@ -294,10 +294,9 @@ var _ = Describe("Workload cluster creation", func() { | |||
}) | |||
}) | |||
|
|||
Context("Creating a Flatcar cluster [OPTIONAL]", func() { | |||
Context("Creating a Flatcar cluster [OPTIONAL]", Ordered, func() { |
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 looks great to me! Just for my own understanding, what does the Ordered
argument mean in this case?
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.
Ordered containers will always run in the order they have been defined.
So in our scenario, all the It()
will always run in the order they have been defined and not messed up by Ginkgo's parallelization approach.
Also note that I converted By()
-> It()
.
By()
acts mostly as a logger. By converting By()
-> It()
I can ask ginkgo to show that Log line as a test case.
More reference on ordered containers : https://onsi.github.io/ginkgo/#ordered-containers
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.
Hey @willie-yao , Wanted to share something I learned the hard way.
Splitting the tests, as I did in here albeit preserving the order of the tests, does not help the testing. Unless the The tests warrants splitting the It
spec into multiple It
s, its better to stick with the existing code flow of using By
inside It
.
The problem with splitting It
s in my case is that, AfterEach()
gets triggered after each It
and it cleans up all the setup the tests does in the first It
.
TL;DR: Use By
in our tests over splitting it into It
since AfterEach()
cleans up setup and other artifacts after each It
.
46ea255
to
f8ad961
Compare
/test pull-cluster-api-provider-azure-e2e-optional |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #3386 +/- ##
==========================================
- Coverage 51.64% 51.63% -0.02%
==========================================
Files 182 182
Lines 18066 18066
==========================================
- Hits 9331 9329 -2
- Misses 8208 8210 +2
Partials 527 527 see 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
1372819
to
efacbb0
Compare
/test pull-cluster-api-provider-azure-e2e-optional |
efacbb0
to
dcd9881
Compare
/test pull-cluster-api-provider-azure-e2e-optional |
dcd9881
to
bef278b
Compare
Any clues why Flatcar tests are still failing? If not, I'll continue investigating. |
This comment was marked as resolved.
This comment was marked as resolved.
/test pull-cluster-api-provider-azure-e2e-optional |
From the artifacts folder, looks like the workload cluster isn't even coming up. |
LGTM label has been added. Git tree hash: 67c766eb3f72afcec7662addf060332e5734218b
|
1 similar comment
LGTM label has been added. Git tree hash: 67c766eb3f72afcec7662addf060332e5734218b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
7af32d1
to
f685b8f
Compare
- Set cloudControllerManager.caCertDir to `/usr/share/ca-certificates` - and check if loadbalancer can spin up successfully - add caCertDir to CCM in tiltfile - add Note about caCertDir to CCM in azure external docs
f685b8f
to
1ed2a41
Compare
Rebased and resolved the Tiltfile conflict. Please take a look. @CecileRobertMichon @willie-yao |
/hold cancel |
/lgtm |
LGTM label has been added. Git tree hash: 450a92ac51af589000ff0e5f451de0111062e774
|
/test pull-cluster-api-provider-azure-e2e-optional |
/cherry-pick release-1.9 |
@nawazkh: #3386 failed to apply on top of branch "release-1.9":
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. |
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.
Sorry for late review. LGTM. Thanks again for the efforts @nawazkh!
@@ -394,6 +394,8 @@ def get_addons(flavor_name): | |||
|
|||
if "intree-cloud-provider" not in flavor_name: | |||
addon_cmd += "; " + helm_cmd + " --kubeconfig ./${CLUSTER_NAME}.kubeconfig install --repo https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo cloud-provider-azure --generate-name --set infra.clusterName=${CLUSTER_NAME}" | |||
if "flatcar" in flavor_name: # append caCetDir location to the cloud-provider-azure helm install command for flatcar flavor |
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.
typo: caCetDir
-> caCertDir
What type of PR is this?
/kind bug
/kind flake
What this PR does / why we need it:
cloud-controller-manager-x-x
pod fails or errors out due to a panic.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #3387
Special notes for your reviewer:
This PR:
caCertDir
while installingcloud provider manager
on a workload cluster.Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: