-
Notifications
You must be signed in to change notification settings - Fork 370
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
Antrea ovs crashes everyday at 00:0x #6046
Comments
@xliuxu I remember you handled the issue before. Have this been fixed? If yes, can you share which version includes the fix? |
I can confirm this issue with the latest UBI image. It is caused by the mismatch user when performing logrotate. We should use https://github.com/openvswitch/ovs/blob/master/rhel/openvswitch-fedora.spec.in#L323 |
Logrotate will run as the user openvswitch, but we start the OVS daemon as the root user. We can disable this behavior by specifying `--without libcapng` in RPM builds. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
Logrotate will run as the user openvswitch, but we start the OVS daemon as the root user. We can disable this behavior by specifying `--without libcapng` in RPM builds. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
Logrotate will run as the user openvswitch, but we start the OVS daemon as the root user. We can disable this behavior by specifying `--without libcapng` in RPM builds. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions of log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: #6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: #6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: #6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: #6046 Signed-off-by: Xu Liu <[email protected]>
logrotate needs to run as the same user as OVS to get the proper permissions for log files. As Antrea runs OVS as root, we disable libcapng to make logrotate also run as root. Fixes: antrea-io#6046 Signed-off-by: Xu Liu <[email protected]>
Describe the bug
antrea-ovs container seems to be crashing everyday in an error state.
To Reproduce
Not clear other than running antrea and letting the log file roll over at 00:00 UTC
Actual behavior
Antrea crahes presumably due to these error messages:
I suspect the log file rolls over and keeps X amount of logs on disk, which it seems like it does not have permissions to do.
All agents crash at the same time so dropped packets has been observed.
Versions:
Openshift 4.12-4.14
antrea/antrea-ubi image is used and it seems all Anrea versions are affected (1.7.1 and onwards at least)
Additional context
We are managing antrea through https://github.com/vmware/antrea-operator-for-kubernetes
The text was updated successfully, but these errors were encountered: