Actions
action #166523
openworker33 log entry "Couldn't write '1' to 'net/ipv4/conf/br1/forwarding', ignoring: No such file or directory" size:S
Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
Start date:
2024-09-09
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
While looking in the logs on worker I found
Sep 08 01:34:22 worker33 systemd-sysctl[1737]: Couldn't write '1' to 'net/ipv4/conf/br1/forwarding', ignoring: No such file or directory
Sep 08 01:34:22 worker33 systemd-sysctl[1737]: Couldn't write '1' to 'net/ipv4/conf/eth0/forwarding', ignoring: No such file or directory
Could be an incomplete path that should start with /
or a race condition if the according prerequisities during a boot are not yet fulfilled. This seems to be related to https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/openvswitch.sls?ref_type=heads#L41 where we write to the forwarding sysctl parameters.
Acceptance criteria¶
- AC1: No error message like the above on all our salt controlled machines
- AC2: openQA jobs on the affected machines can still reach the internet
Suggestions¶
- Investigate the impact.
- Maybe this affects multi-machine tests - which are currently limited
- Check dependencies between systemd-sysctl (which sets this attribute) and wicked (or whichever service creates br1)
- Lookup why this is a warning and not a failure of the service (or any service)
- Read systemd-sysctl-related documentation
Updated by okurz 3 months ago
- Subject changed from worker33 log entry"Couldn't write '1' to 'net/ipv4/conf/br1/forwarding', ignoring: No such file or directory" to worker33 log entry "Couldn't write '1' to 'net/ipv4/conf/br1/forwarding', ignoring: No such file or directory" size:S
- Description updated (diff)
- Status changed from New to Workable
Actions