Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 103110

Summary: irqbalance always deleted in preuninstall
Product: [Retired] Red Hat Raw Hide Reporter: Kaj J. Niemi <kajtzu>
Component: kernel-utilsAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.4-8.39 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-22 16:48:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 100643    

Description Kaj J. Niemi 2003-08-26 17:05:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:

Shouldn't the irqbalance part be INSIDE the conditional? Otherwise we delete it
on upgrades as well... right?

if [ "$1" = "0" ] ; then
 /sbin/service smartd stop
 /sbin/chkconfig --del microcode_ctl
 /sbin/chkconfig --del smartd
fi
 /sbin/chkconfig --del irqbalance


Version-Release number of selected component (if applicable):
kernel-utils-2.4-8.31

How reproducible:
Always

Steps to Reproduce:
1. I guess?
2.
3.
    

Additional info:
Seems to have gotten disabled somehow on all systems with an upgraded
kernel-utils package.

Comment 1 Michael K. Johnson 2003-10-21 20:49:17 UTC
kernel-utils-2.4-8.39 has this fixed, along with a bunch of other things...
Should be in next rawhide.

Of course, it will still get removed on upgrade to that package, but after
that is fixed, the *next* update beyond that should be OK.