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
Fix monitoring test failure due to missing CRBs #11541
Conversation
Skipping CI for Draft Pull Request. |
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
5 similar comments
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.28-sig-monitoring |
@assafad: 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. |
96d7771
to
660228a
Compare
/test pull-kubevirt-e2e-k8s-1.28-sig-monitoring |
@assafad: 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-kubevirt-e2e-k8s-1.29-sig-monitoring |
2 similar comments
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring |
@@ -198,8 +198,10 @@ func UpdateKubeVirtConfigValue(kvConfig v1.KubeVirtConfiguration) *v1.KubeVirt { | |||
patch, err := strategicpatch.CreateTwoWayMergePatch(old, newJson, kv) | |||
Expect(err).ToNot(HaveOccurred()) | |||
|
|||
kv, err = virtClient.KubeVirt(kv.Namespace).Patch(kv.GetName(), types.MergePatchType, patch, &metav1.PatchOptions{}) | |||
Expect(err).ToNot(HaveOccurred()) | |||
Eventually(func() error { |
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.
@assafad Can you please explain why this is necessary? IIUC the issue was with handling cluster role bindings
660228a
to
d555a81
Compare
@assafad: The following tests failed, say
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. |
Signed-off-by: assafad <aadmi@redhat.com>
d555a81
to
de52207
Compare
closing in favor of #11506. |
What this PR does
Before this PR:
e2e monitoring tests are flaky due to outdated configs, because some times pods don't have necessary permissions to access resources.
After this PR:
no longer flaky.
Fixes https://issues.redhat.com/browse/CNV-38827
Special notes for your reviewer
Same fix as done by #11506 for release-1.1.
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note