Description of problem: Refer to bug 146415 for some background on this, but basically the kernel-utils that we shipped in RHEL4GA incorrectly had microcode_ctl disabled by default in all runlevels. We're releasing kernel-utils-2.4-13.1.64 in U1 which fixes this for new installations (i.e. has correct chkconfig declarations) but on upgrade the initscripts aren't going to get touched (by design I might add) and microcode_ctl will still be disabled for all runlevels. So the question is do we want to fix "broken initscripts" in U2 or not. I'm not entirely sure this is worth fixing, as there's really no way to get it right, as overriding it outright would blow the case where the user chose to disable the microcode_ctl service. Anyway, throwing in a U2 request bug in case Intel decides they want to see this fixed so that the service gets started on upgrade. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Jay, .64 has a trigger that should fix this, so this may even be fixed already.
Two things with the .64 packages. First, the call to chkconfig should be 'chkconfig microcode_ctl reset' Second, I don't think a %triggerpostun is going to work (actually, I know it isn't, as just tried it.) That would only work if the old kernel-utils were removed after the trigger were registered, which isn't what's happening. That having been said, since this is the first version of the package which is going to have the correct initscripts declaration, you can just put '/sbin/chkconfig microcode_ctl reset' in the %post. By that time the correct initscript file has been laid down on the filesystem and the 'reset' will pick it up. Of course this isn't fullproof, as we'll need to remove the 'reset' from the next version of the package, so anyone going from old kernel-utils to <new+1> won't get the benefit of the fix, but I really don't see a way around it. We can't register the trigger without someone installing the package.
good catch. I'm building .65 now with '--reset' changed to 'reset'
Can you double check that .65 doesnt work before I try moving this to %post please ? (I'll check myself later when I get to the office if you haven't tested by then).
Sorry, should have been more explicit. The %triggerpostun isn't working as expected, at least not in my testing.