Bug 845294

Still present in RC2!

I'm using this simple autoyast.xml

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
  <firewall>
    <start_firewall config:type="boolean">false</start_firewall>
  </firewall>
</profile>

BTW, when generating an autoyast.xml from "yast2 autoyast", it does not generate 
"<enable_firewall>", only the <start_firewall>"

Isn't full autoyast functionality critical?

Lukas someone needs to look at autoyast interface for yast2-firewall.
Currently there is mo maintainer for this module.

Michal, seems to be affected by your changes in Network, or am I wrong?

Probably yes.

I did a fix for enabling/disabling firewall during installation. But it didn't make it for 13.1 release. So, please retest against factory image.

There is no factory image available openSUSE-UNTESTED contains the same
images as 13.1 GM. Could you tell me the git hash of the fix so I can test it.

I retried this now with 13.1 GA and for me it works as expected.

When using

  <firewall>
    <enable_firewall config:type="boolean">false</enable_firewall>
    <start_firewall config:type="boolean">false</start_firewall>
  </firewall>

There is no firewall running at end of installation.
When using "yast2 clone_system" in the installed system, the created 
firewall section is also fine. Maybe the observed problems were caused
by missing code for runlevel module in 13.1 RC.

To Original reporter (Luiz), please recheck with 13.1 GA and reopen with new 
y2log files when problem still exists.

Firewall is disabled as configured. I used the configuration in comment 1 but I had to add firewall package manually.

"yast2 autoyast" suggests to use only 
"<start_firewall config:type="boolean">false</start_firewall>".
It really does not make sense to start and enable. And it worked as expected.

Indeed, there is still a problem with the suggested configuration GUI. After initial autoyast scripts, I get a screen that allows me to reconfigure some stuffs. In this first screen, firewall is still marked as enabled. The same problem happens with root password.

Ok, so it was a misunderstanding and like with root password you
mention the misleading text at overview screen before installation 
starts. This is the same as with root password services set up in
second stage (like root password and firewall) do not have right
settings. Simply since firewall config is applied after first boot of
installed system and not while install environment is still running.

The problem with wrongly created xml file I cannot reproduce when
I start "yast2 autoyast" I correctly get

 <firewall>
    <enable_firewall config:type="boolean">false</enable_firewall>
    <start_firewall config:type="boolean">false</start_firewall>
  </firewall>

Which package did you need to install manually?

Yes, as "overview screen" shows a different info, firewall might have been fixed some time before.

For the XML:

Run: /sbin/yast2 autoyast

Go to Security/firewall/edit, select "Disable...", OK.
Go to Menu/View/Source

You get:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
  <deploy_image>
    <image_installation config:type="boolean">false</image_installation>
  </deploy_image>
  <firewall>
    <start_firewall config:type="boolean">false</start_firewall>
  </firewall>
</profile>

Is it wrong? I though it was just simplified :)

The autoyast conf posted in comment 1 does not select packages. This makes tests faster than a normal installation. However, nothing required SuSEfirewall2 (but yast2-firewall was selected). I guess yast2 might ask to install it if I open "yast2 firewall". If so, I see no problem at all. If not, yast2-firewall should require SuSEfirewall2.

Anyway, The "overview screen" needs some love. Besides not showing autoyast firewall state (as it does with root password), if installation without firewall is allowed, "overview screen" should even omit/disable its config.