Comment # 6 on bug 1036590 from Matthias Gerstner

(In reply to lslezak@suse.com from comment #5)

> And that's correct IMHO, during upgrade YaST should keep the previous status
> and do not touch the service. If it was disabled by user is should stay
> disabled.

The thing here is that in 12.2 the SuSEfirewall2 is still a SysV init script.
In this upgrade scenario the SysV init script was enabled before upgrade and
after upgrade we end up with a disabled systemd service.

This has worked before a recent SuSEfirewall2 update. But I fail to find the
logic in YaST that made this work before. Without knowing the mechanism I have
currently no idea which change in SuSEfirewall2 caused this regression.

Do you have some more pointers for me?

Thank you for your input.