Comment # 1 on bug 1091649 from Lukas Ocilka

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.

> * **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.

I'm sorry.

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.