What | Removed | Added |
---|---|---|
Status | IN_PROGRESS | RESOLVED |
Resolution | --- | FIXED |
(In reply to - - from comment #54) > Workarounds are solutions by definition. Poor solutions. So you consider the addition of the two kernel patches above a poor solution? Sorry to hear that, I thought it was quite a good one. > Anyway, I can confirm that the issue has been solved in the Tumbleweed > 20190115 snapshot: > kernel-default-4.20.0-1.5.x86_64 > systemd-239-3.1.x86_64 > dracut-044.1-22.1.x86_64 > > The error messages have stopped appearing. OK, great. > > @all, do we have a fool-proof setup procedure for a VM to reproduce this problem? > > I suspect that the issue affects every system where bpfilter_umh is started, > but verbose errors appear only if the dracut's shutdown hook is enabled. I haven't yet figured out which service starts the bpfilter_umh process. Have you? I suspected firewalld, but I've seen bpfilter_umh running on systems with firewalld disabled. Closing the bug per comment 48, 51, and 54.