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

Add CI testing for Fedora & CentOS #3552

Open
tstromberg opened this issue Jan 19, 2019 · 12 comments
Open

Add CI testing for Fedora & CentOS #3552

tstromberg opened this issue Jan 19, 2019 · 12 comments
Labels
area/testing kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@tstromberg
Copy link
Contributor

This should help us detect issues like #3498

@tstromberg tstromberg added area/testing priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jan 23, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2019
@tstromberg tstromberg added r/2019q2 Issue was last reviewed 2019q2 and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 22, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2019
@tstromberg tstromberg added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 19, 2019
@tstromberg
Copy link
Contributor Author

Still a valid issue.

@tstromberg tstromberg added the kind/process Process oriented issues, like setting up CI label Sep 20, 2019
@tstromberg tstromberg added this to the v1.7.0-candidate milestone Dec 9, 2019
@medyagh
Copy link
Member

medyagh commented Dec 16, 2019

we still need to do this issue !

@afbjorklund
Copy link
Collaborator

From the number of issues reported, it seems like CentOS is more important to test than Fedora...

@tstromberg tstromberg changed the title Add CI testing for Fedora Add CI testing for Fedora & CentOS Jan 6, 2020
@tstromberg
Copy link
Contributor Author

@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.

@afbjorklund
Copy link
Collaborator

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...

systemd.unified_cgroup_hierarchy=0

@afbjorklund
Copy link
Collaborator

Any progress on this ?

@blues-man
Copy link
Contributor

+1

@tstromberg tstromberg removed the priority/backlog Higher priority than priority/awaiting-more-evidence. label Nov 6, 2020
@tstromberg
Copy link
Contributor Author

Bumping this up because we've seen some Fedora 32 specific issues recently.

@afbjorklund
Copy link
Collaborator

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.

@priyawadhwa
Copy link

priyawadhwa commented Feb 18, 2021

we still want to do this, at the minimum with the docker driver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

8 participants