Comment # 1 on bug 1118044 from Matthias Gerstner

Thank you for opening the bug report. Well this can only happen in Tumbleweed
currently due to the rolling release model creating states that nobody has
foreseen. As explained in bug 1091968, the upgrade path should work by keeping
SuSEfirewall2 installed. This seems to have worked in this case here, too, but
since openssh dropped the service file, the ssh port can no longer be opened.

>From the side of SuSEfirewall2 there is little I can do. The service
definitions are provided by the other packages and there are no hard coded
ones found in there.

You could either ask the openssh maintainers to keep this service file
packaged a while longer for reasons of backwards compatibility. Or
SuSEfirewall2 could take over ownership of this file. But this creates other
troubles like a possible conflict between SuSEfirewall2 and openssh.

Or do you see any other approaches to fix this?