Skip to content
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

[Backport 1.28-strict] CI: Fix addons CI (#4913)(#4923) #4932

Open
wants to merge 3 commits into
base: 1.28-strict
Choose a base branch
from

Conversation

louiseschmidtgen
Copy link
Contributor

Description

This PR fixes the addons-CI by changing the distro in the test and pinning pytest. For further info please refer to the back-ported PRs.

ktsakalozos and others added 3 commits March 7, 2025 12:08
Currently, the "Test core addons" job fails because the test_cis test
fails, having 2 more warnings than expected.

Those warnings are from ``microk8s kube-burner``, which has the following
new warnings (the checks were passing before):

```
[WARN] 2.3 Ensure that the --auto-tls argument is not set to true (Automated)
[WARN] 2.6 Ensure that the --peer-auto-tls argument is not set to true (Automated)
``

Those warnings appear because the commands used for checking them fail:

```
2.3 audit test did not run: failed to run: "/bin/ps -ef | /bin/grep k8s-dqlite | /bin/grep -v grep", output: "", error: exit status 1
2.6 audit test did not run: failed to run: "/bin/ps -ef | /bin/grep k8s-dqlite | /bin/grep -v grep", output: "", error: exit status 1
```

Those errors would suggest that there is no ``k8s-dqlite`` process running
on the node... but it should. In ``test_cis``, after enabling
``cis-hardening`` (``microk8s enable cis-hardening``) and before running
``microk8s kube-burner``, in the test we're waiting for Kubernetes to be
available, accesible, and ready (``wait_for_installation``), which would only
be possible if ``k8s-dqlite`` would be running. What's more, this issue
does not occur when manually running the exact same commands as in the
GitHub action, even on the same GitHub Runners.

Pinning pytest to 8.3.4 seems to be solving the issue above (8.3.5 was released
a few days ago).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants