-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add CI testing for Fedora & CentOS #3552
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Still a valid issue. |
we still need to do this issue ! |
From the number of issues reported, it seems like CentOS is more important to test than Fedora... |
@afbjorklund - VM's are cheap, so we may as well do both. The idea was that Fedora would find breaking changes sooner, by the nature of the distribution. |
Currently Fedora is thoroughly broken for kubernetes, since they have changed to cgroups v2. See https://fedoraproject.org/wiki/Changes/CGroupsV2 So I guess (for now), that we would have to revert such a Fedora 31 VM to use cgroups v1 instead...
|
Any progress on this ? |
+1 |
Bumping this up because we've seen some Fedora 32 specific issues recently. |
Here is the configuration that I have been using: sudo yum install -y net-tools conntrack-tools
# revert /usr/lib/sysctl.d/00-system.conf
cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sudo sysctl --system
# setenforce 0
sudo sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
# cgroups v1: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1757078
sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0" For the vagrant provisioner of centos/fedora 32. |
we still want to do this, at the minimum with the docker driver |
This should help us detect issues like #3498
The text was updated successfully, but these errors were encountered: