Open agentpoyo opened 1 year ago
This is also happening running the new sig_term_handled
test.
May need some help to reproduce this. The test runs as expected on Ubuntu 22.04.
I'll try running it a few times to see if this test fails randomly.
@agentpoyo Was able to reproduce the bug with the sig_term_handled
test.
The issue for sig_term_handled test was the sample CNF that was being used. It was the CNF used in the specs for the test.
PodDisruptionBudget
version was policy/v1beta
earlier. Since K8s 1.25, this is now policy/v1
. I updated the sample CNF and pushed a change for GitHub Actions to run. That will confirm my assumption if the specs work as expected.
Confirmed. The issue is actually about the k8s version. It won't be caught on GitHub Actions.
PodDisruptionBudget policy/v1beta
was removed from k8s 1.25. So sample CNFs that use this have to be updated. I'll create a ticket for this.
This might be the reason why this issue isn't caught on GitHub Actions.
@HashNuke is this issue still relevant?
@lixuna Yes. This issue is still relevant.
I just re-read the details and checked the attached commit on this ticket.
There's a branch bug/1753
with some unmerged changes but that requires other work updating kind on github actions. We can let any of the contributors help resolve this since one of them is already working on kind-related issues.
I was confused when I saw Denver's commit on this ticket and thought this was fixed. The commit is attributed to Denver, but that was actually me committing and pushing on the pair machine.
PodDisruptionBudget
(see attached screenshot that makes note of the change required).The following changes have to be done in the one PR.
PodDisruptionBudget
.I've added a contributions-welcome
tag to this ticket so that anyone interested can pick this up to lend a hand.
Describe the bug Operator Framework gives hash key "kind" error when running on latest Ubuntu client
To Reproduce Setup CNF-Testsuite on latest Ubuntu 22.04 (this might be occurring on other OSes as well)
Expected behavior This spec test to verify operator framework should not fail with crystal hash errors
Error
Device (please complete the following information):