Bug 482532

Summary:	cannot disable SuSEfirewall2_init/SuSEfirewall2_setup
Product:	[openSUSE] openSUSE 11.1	Reporter:	Olli Artemjev <grey-olli>
Component:	YaST2	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P3 - Medium	CC:	grey-olli, locilka
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	requested yast2 logs. Runlevel editor started, SuSE_firewall* disabled, changes applied, then runlevel editor is started again - SuSE_firewall* are on the same place (runlevel 3, 5).

Description Olli Artemjev 2009-03-05 19:17:31 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6

On one of my PCs I'm using my own firewall script. I was unable to remove  SuSEfirewall2_init and SuSEfirewall2_setup using runlevel editor - the checkboxses are all removed for both services, but when I do save current state & then start runlevel editor again both services are checked as used (checkboxes enabled). I've removed both scripts from init.d, but that is ugly solution.

Reproducible: Always

Steps to Reproduce:
1. Remove  SuSEfirewall2_init  & SuSEfirewall2_setup via runlevel editor, save.
2. run runlevel editor again: the  SuSEfirewall2_init & SuSEfirewall2_setup are enabled.
Actual Results:  
cannot disable SuSEfirewall2_init/SuSEfirewall2_setup

Expected Results:  
SuSEfirewall2_init  & SuSEfirewall2_setup should be removable by runlevel editor.

Comment 1 Cyril Hrubis 2009-03-09 15:36:55 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Comment 2 Olli Artemjev 2009-03-15 13:50:56 UTC

Created attachment 279645 [details]
requested yast2 logs. Runlevel editor started, SuSE_firewall* disabled, changes applied, then runlevel editor is started again - SuSE_firewall* are on the same place (runlevel 3, 5).

Comment 3 Lukas Ocilka 2009-03-17 11:35:10 UTC

I've reproduced this issue and it seems it caused by insserv that doesn't handle runlevel 4 (yes, we somehow support it) correctly.

Scripts, and their default-start options:

  * SuSEfirewall2_setup
    # Default-Start:  3 4 5

  * SuSEfirewall2_init
    # Default-Start:  3 4 5

According to logs and my testing, Runlevel Editor was calling these commands:

  * /sbin/insserv -f /etc/init.d/SuSEfirewall2_init,start=4

  * /sbin/insserv -f /etc/init.d/SuSEfirewall2_setup,start=4

...because user manually disabled the service in runlevels 3 and 5 (but not in runlevel 4 which is not visible in that case - visibility defined in control file, see FATE #303798).

A workaround to fully disable a service is to click on [Disable] button in non-expert configuration in Runlevel Editor. Anyway, insserv should disable the services in all but runlevel 4 which it doesn't and keeps it enabled in all default runlevels.

Comment 4 Dr. Werner Fink 2009-03-30 12:53:59 UTC

it's a dup

*** This bug has been marked as a duplicate of bug 470654 ***