http://bugzilla.suse.com/show_bug.cgi?id=1091968 http://bugzilla.suse.com/show_bug.cgi?id=1091968#c1 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |matthias.gerstner@suse.com Resolution|--- |INVALID --- Comment #1 from Ludwig Nussel --- well, obviously it is still supported in maintenance mode as a full migration is not possible. if it was unsupported it would not be in the repo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1091968 http://bugzilla.suse.com/show_bug.cgi?id=1091968#c3 --- Comment #3 from Matthias Gerstner --- This topic seems still to be a source of confusion. I discussed this with firewalld maintainer Markos Chandras a while ago and it turned out that the migration from SuSEfirewall2 to firewalld using his helper packages "susefirewall2-to-firewalld" is only possible if both firewalls are installed. This means that removing SuSEfirewall2 will break this migration path. I asked Markos to check if an offline migration would not also be possible but I don't know if he found time to implement it. I even tried to introduce a Conflicts to achieve removal of SuSEfirewall2 after upgrading but this only resulted in more troubles as outlined in bug 1084177 and bug 1085260. So as far as I understand it at the moment: - SuSEfirewall2 should *not* be forcibly removed after upgrade to support the upgrade path using susefirewall2-to-firewalld - sadly, if both firewalls are installed and *enabled* in systemd then strange things can happen (on systemd level the two firewalls can preempt each other multiple times). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1091968 http://bugzilla.suse.com/show_bug.cgi?id=1091968#c4 Matthias Gerstner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Matthias Gerstner --- Since there is no more protest or suggestions and Leap 15.0 is arleady released I think we can close this bug. Removal of SuSEfirewall2 is not feasible due to the migration path, difficulties can result from this in some cases that have to be resolved manually. -- You are receiving this mail because: You are on the CC list for the bug.