http://bugzilla.suse.com/show_bug.cgi?id=1036590
http://bugzilla.suse.com/show_bug.cgi?id=1036590#c8
Michal Filka
(In reply to Matthias Gerstner from comment #6)
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.
Maybe then there was some change in some migration script. Actually I do not know how the migration from init to systemd works...
This has worked before a recent SuSEfirewall2 update. But I fail to find the logic in YaST that made this work before.
No, there is no such logic AFAIK. YaST does not touch the service during upgrade, the code above shows that the firewall is configured only during installation.
Michal, any comments?
y2network do not touch any network configuration in "common" upgrade scenario. All automatic configuration which is done during clean installation should be disabled in case of upgrade workflow. -- You are receiving this mail because: You are on the CC list for the bug.