Comment # 2 on bug 1036590 from Matthias Gerstner

Thanks for the report.

The only change in sr#483163 related to the startup of SuSEfirewall2 that
comes to my mind would be this one:

> --- SuSEfirewall2_init.service
> +++ SuSEfirewall2_init.service
> @@ -3,6 +3,8 @@
>  Before=network.service
>  DefaultDependencies=false
>  Requires=sysinit.target
> +After=sysinit.target
> +RequiresMountsFor=/dev/shm
>  Conflicts=firewalld.service

So if for some reason in the openQA context the sysinit.target is not reached
or mounting of /dev/shm does not happen then this might explain the failing
test.

I've tested a minimal server install of
openSUSE-Tumbleweed-NET-x86_64-Snapshot20170429-Media.iso and after installing
and enabling SuSEfirewall2 everything works as expected. After reboot the
firewall is up.

However, the firewall is not installed and enabled by default. The installer
doesn't ask about it. Don't know why that is different in Tumbleweed than in
other SUSE distros.

Who is supposed to install and enable SuSEfirewall2 in the openQA setup? Where
does it happen?