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

Fix CI #229

Open
ayr-ton opened this issue Oct 15, 2024 · 5 comments
Open

Fix CI #229

ayr-ton opened this issue Oct 15, 2024 · 5 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@ayr-ton
Copy link
Collaborator

ayr-ton commented Oct 15, 2024

GitHub actions are failing for 5 months, it needs reconfiguration for running new actions.

@ayr-ton ayr-ton added the bug Something isn't working label Oct 15, 2024
@ayr-ton ayr-ton self-assigned this Oct 15, 2024
@ayr-ton ayr-ton added good first issue Good for newcomers and removed good first issue Good for newcomers labels Oct 15, 2024
@ayr-ton
Copy link
Collaborator Author

ayr-ton commented Oct 20, 2024

Current log is:

Oct 20 04:15:38 node1 k3s[9576]: time="2024-10-20T04:15:38Z" level=fatal msg="failed to find cpuset cgroup (v2)"

The most recent stable versions deprecated cgroup v1 and now are working only with v2.
Trying to fix molecule to work with v2 both locally and in GitHub Actions.

@ayr-ton ayr-ton removed their assignment Oct 20, 2024
@ayr-ton ayr-ton added the help wanted Extra attention is needed label Oct 20, 2024
Copy link

stale bot commented Jan 3, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Jan 3, 2025
@InRiPa
Copy link

InRiPa commented Jan 5, 2025

Hi @ayr-ton ,

I'm not sure if I got the same issue. But it seems i get some problems with cgroup as well, using cgroup2fs (instead of v1).

TASK [xanmanning.k3s : Check if memory cgroup is enabled] *************************************************************************************************************************************
ok: [k3s-master001] => {"changed": false, "cmd": ["grep", "-E", "^memory\\s+.*\\s+1$", "/proc/cgroups"], "delta": "0:00:00.010149", "end": "2025-01-05 19:54:37.486317", "failed_when_result": false, "msg": "non-zero return code", "rc": 1, "start": "2025-01-05 19:54:37.476168", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

TASK [xanmanning.k3s : Fail if memory cgroup is not enabled] **********************************************************************************************************************************
fatal: [k3s-master001]: FAILED! => {
    "assertion": "k3s_check_cgroup_option.rc == 0",
    "changed": false,
    "evaluated_to": false,
    "msg": "memory cgroup disabled. If you are running on a Raspberry Pi, see:\nhttps://rancher.com/docs/k3s/latest/en/advanced/#enabling-cgroups-for-raspbian-buster\n"
}

PLAY RECAP ************************************************************************************************************************************************************************************
k3s-master001              : ok=8    changed=0    unreachable=0    failed=1    skipped=3    rescued=0    ignored=0   

memory is indeed not listed there (anymore?). Now, I wonder would a check of the following fix this?
cat /sys/fs/cgroup/cgroup.controllers | grep 'memory'

@stale stale bot removed the wontfix This will not be worked on label Jan 5, 2025
@dbrennand
Copy link
Contributor

dbrennand commented Jan 5, 2025

Hi @ayr-ton ,

I'm not sure if I got the same issue. But it seems i get some problems with cgroup as well, using cgroup2fs (instead of v1).

TASK [xanmanning.k3s : Check if memory cgroup is enabled] *************************************************************************************************************************************

ok: [k3s-master001] => {"changed": false, "cmd": ["grep", "-E", "^memory\\s+.*\\s+1$", "/proc/cgroups"], "delta": "0:00:00.010149", "end": "2025-01-05 19:54:37.486317", "failed_when_result": false, "msg": "non-zero return code", "rc": 1, "start": "2025-01-05 19:54:37.476168", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}



TASK [xanmanning.k3s : Fail if memory cgroup is not enabled] **********************************************************************************************************************************

fatal: [k3s-master001]: FAILED! => {

    "assertion": "k3s_check_cgroup_option.rc == 0",

    "changed": false,

    "evaluated_to": false,

    "msg": "memory cgroup disabled. If you are running on a Raspberry Pi, see:\nhttps://rancher.com/docs/k3s/latest/en/advanced/#enabling-cgroups-for-raspbian-buster\n"

}



PLAY RECAP ************************************************************************************************************************************************************************************

k3s-master001              : ok=8    changed=0    unreachable=0    failed=1    skipped=3    rescued=0    ignored=0   


memory is indeed not listed there (anymore?). Now, I wonder would a check of the following fix this?

cat /sys/fs/cgroup/cgroup.controllers | grep 'memory'

Hi @InRiPa - What OS/distribution are you seeing this issue with?

@InRiPa
Copy link

InRiPa commented Jan 5, 2025

Hi @dbrennand ,
happened on an Arch Linux server after updating it today (attempted to update k3s as well).

cat /proc/cgroups 
#subsys_name	hierarchy	num_cgroups	enabled
cpu	0	198	1
cpuacct	0	198	1
blkio	0	198	1
devices	0	198	1
freezer	0	198	1
net_cls	0	198	1
perf_event	0	198	1
net_prio	0	198	1
hugetlb	0	198	1
pids	0	198	1
rdma	0	198	1
misc	0	198	1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants