-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[Flaking-Test] VPA - pkg/admission-controller/certs_test.go #7831
Comments
/triage accepted |
This seems strange. I looked into the code that was writing the cert, and it seems fine to me. I also checked the filesystem on GitHub Actions at /tmp, and it's a regular ext4 filesystem. I tried to reproduce this locally, but couldn't get it to fail |
@adrianmoisey could it be something related to the runner's OS? We're using |
I highly doubt it, since it's a VM running a stable OS and a stable filesystem. One option is to run a test, in a loop, on GitHub Actions. That could help test it |
Good idea |
Another similar flake: https://github.com/kubernetes/autoscaler/actions/runs/13314589637/job/37185375732?pr=7834
|
Ill try to dig into this in the future but any help will be appreciated. |
@omerap12: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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-sigs/prow repository. |
This happened again: https://github.com/kubernetes/autoscaler/actions/runs/13444469376/job/37566506181?pr=7813 Similar flake to the previous one:
|
/assign I'm intrigued now. |
The recent PR #7454 introduced a feature that allows the VPA admission controller to reload the caBundle certificate and patch the webhook. Since its merge, we've observed a flaky test that was added in the same PR.
The test TestUnchangedCAReloader intermittently fails with the following error:
A failure from a recent run can be seen here: GitHub Actions Run.
It appears the test is failing due to intermittent certificate reload issues and unexpected patch invocations. Further investigation is needed to determine the root cause and stabilize the test.
/area vertical-pod-autoscaler
/kind flake
The text was updated successfully, but these errors were encountered: