-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 [e2e framework] Fix race condition when testing ClusterResourceSetBinding #3394
Conversation
/assign @sedefsavas |
} | ||
|
||
if err := input.ClusterProxy.GetClient().Get(ctx, types.NamespacedName{Name: resource.Name, Namespace: input.ClusterResourceSet.Namespace}, configSource); err != nil { | ||
continue |
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.
@sedefsavas I'm not overly familiar with these tests, so I wasn't sure if it was intentional that we continued through the loop when the Get for the related Secret/ConfigMap returned an error, so I kept the existing behavior. I'm wondering if this should return false
here instead, though.
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.
If the resource is missing, CRS will not requeue but retry at each reconcile, because this is not an error. So, we are only interested in seeing the resources that exist to be applied by CRS.
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.
Can we add a comment to that effect?
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 test is going to be removed totally with this PR: #3332
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.
Are we planning to merge that in v0.3.8, or later? If later, I'd prefer to have a comment just in case it stays around for longer
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.
There are changes in providers as well and all need to go in at once.
We are waiting CAPA's next release, there is a change there we need to wait.
/milestone v0.3.8 |
/lgtm |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
/retest |
…ding - Also, update commment on test/framework/clusterresourceset_helpers.go
/lgtm |
/test pull-cluster-api-e2e e2e failures look like flakes that are not related to this PR: /test pull-cluster-api-e2e |
/test pull-cluster-api-e2e |
What this PR does / why we need it:
Attempts to fix a race condition in the test framework related to ClusterResourceSetBindings