http://bugzilla.opensuse.org/show_bug.cgi?id=1198214 Bug ID: 1198214 Summary: 15.3, firewalld mostly doesnt autostart on bootup any more - since february 2022, Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: abittner@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- 15.3, x64, multiple ethernet interfaces, simple ipv4 router nat machine. ever since sometime in february 2022, when rebooting the machine, firewalld doesnt succeed to start up on reboot or startup any more even though its set as enabled. using wicked on this machine, been a long history of previous opensuse suse updates and upgrades with this machine, right now its on opensuse 15.3 leap. one ethernet interface (its address) is on dhcp4 shown in yast, the other ethernet interface is fixed ipv4 assigned to it. journalctl -u firewalld.service shows the following in february 2022, and then ever since, but not always all the time warning not enabled eth0 warning not enabled eth1 and as of end of march 2022 even such red lines and details about: firewalld[2914]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', Fals> I need to ssh connect to the machine then and fire up the firewalld service manually. Even though it is at enabled (vendor preset disabled). What happened as of february 2022 and what happend at the end of march for those red status lines? this machine and its firewalld worked perfectly for many years, and a long time in 15.3 up until february 2022. how to find out more about whats happening? ty. -- You are receiving this mail because: You are on the CC list for the bug.