http://bugzilla.suse.com/show_bug.cgi?id=1043446 http://bugzilla.suse.com/show_bug.cgi?id=1043446#c1 Michal Filka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmader2@gmu.edu, | |mfilka@suse.com Flags| |needinfo?(jmader2@gmu.edu) --- Comment #1 from Michal Filka --- Thanks for report. Could you please attach yast2 logs which cover first boot issue? Pls see https://en.opensuse.org/openSUSE:Report_a_YaST_bug -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1043446 http://bugzilla.suse.com/show_bug.cgi?id=1043446#c2 Jason Mader changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jmader2@gmu.edu) | --- Comment #2 from Jason Mader --- Created attachment 728673 --> http://bugzilla.suse.com/attachment.cgi?id=728673&action=edit YaST2 logs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1043446 http://bugzilla.suse.com/show_bug.cgi?id=1043446#c4 --- Comment #4 from Jason Mader --- I have just cloned the firewall config, but it’s the same as my autoyast config. I don’t know what you mean by special flags. I am reporting that only after the first boot of autoyast configuration is the SuSEfirewall2 in Leap 42.3 still have closed 22/tcp. The configuration is set, because a restart of SuSEfirewall2 has the correct configuration. (In reply to Lukas Ocilka from comment #3)

Wild guess, you need to really open a ssh port in firewall instead of using those special flags that are there just for the manual installer. These two flags are coming from control file, not from AytoYast profile. Try cloning the Firewall configuration on your system and you will see.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1043446 http://bugzilla.suse.com/show_bug.cgi?id=1043446#c6 --- Comment #6 from Jason Mader --- It does not help in Build0277. (In reply to Lukas Ocilka from comment #5)

So, as a hotfix, I'd propose you to add

<service>SuSEfirewall2<service>

into <services> section. That might but might not help...

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1043446 http://bugzilla.suse.com/show_bug.cgi?id=1043446#c17 Knut Alejandro Anderssen González changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(mfilka@suse.com), | |needinfo?(knut.anderssen@su | |se.com) | --- Comment #17 from Knut Alejandro Anderssen González --- (In reply to Jason Mader from comment #16)

Well, SuSEfirewall2 isn't used in Leap 15.0 and the new firewall opens the ssh port as needed. I suppose this can be closed.

Although it is not present in Leap15.0 this bug was fixed as consequence of a duplicate one in SLE (bsc#1080630), so it should be already fixed by this packages: openSUSE Leap 42.3 (src): yast2-3.2.45-2.6.1, yast2-network-3.2.51-9.1 The fix was added and described in this PR: https://github.com/yast/yast-network/pull/608 -- You are receiving this mail because: You are on the CC list for the bug.