http://bugzilla.suse.com/show_bug.cgi?id=1091649
http://bugzilla.suse.com/show_bug.cgi?id=1091649#c2
Oliver Kurz
SuSEfirewall2 is no loner supported by YaST.
## Expected result * **E1:** The old configuration module should exist as long as SuSEFirewall2 exists on the system
Wrong assumption. The old configuration for SuSEfirewall2 will never exist on 15-based system. The feature did not specify that, and if it did, we would never accept it.
I do not understand what you mean. What assumption did I make? I mentioned migrated/upgraded systems.
* **E2:** The new `yast2 firewall` should mention that it applies only to the new firewalld based implementation, not just "the firewall"
It applies to the ONLY firewall on 15-based system. I don't know what the test does as YaST logs are not attached, but if it just preserves SuSEfirewall2 during upgrade, then you can simply delete the test. This is not a supported scenario.
CCing Tumbleweed and Leap RMs to give their thought here. https://openqa.opensuse.org/tests/667584#downloads shows the logs from this test scenario. Upgrade from an older Tumbleweed where SuSEfirewall2 is installed to a more recent Tumbleweed which ships the newer firewalld yast configuration part is certainly supported in openSUSE. I don't think we will delete the test. There is currently no "very old Tumbleweed to current Tumbleweed" automated test but the "old leap to current Tumbleweed" simulate that still.
But you can maybe open another bug: The system should scram loudly that SuSEfirewall2 is not supported and should try hard deleting it. Anyway, that's a product specific behavior/feature and not a YaST task.
Ok, I did: https://bugzilla.suse.com/show_bug.cgi?id=1091968 This might be certainly a good alternative. -- You are receiving this mail because: You are on the CC list for the bug.