Bug 437873 - Sevice run level enablment of NetworkManager & network not preserved on update
Sevice run level enablment of NetworkManager & network not preserved on update
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: NetworkManager (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2008-03-17 16:26 EDT by Tim Burke
Modified: 2009-01-20 16:28 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 16:28:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:0161 normal SHIPPED_LIVE NetworkManager enhancement and bug fix update 2009-01-20 11:05:18 EST

  None (edit)
Description Tim Burke 2008-03-17 16:26:33 EDT
Tim Burke (tburke@redhat.com) said: 
> > Hi Dan & Bill,
> >
> > I just did a `yum update` from RHEL5.1 -> 5.2 beta.  After doing that my 
> > wireless didn't just magically work.
> >
> > Looked to me that the network services didn't preserve the prior run level 
> > enablement:
> >
> > [root@localhost ~]# chkconfig --list | grep -i network
> > NetworkManager  0:off   1:off   2:off   3:on    4:on    5:on    6:off
> > NetworkManagerDispatcher        0:off   1:off   2:off   3:off   4:off   
> > 5:off  6:off
> > network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
> >
> > [root@localhost ~]# chkconfig network off
> > [root@localhost ~]# chkconfig NetworkManagerDispatcher on
> > followed by reboot corrected this.
> >
> > Question: is this the expected behavior?  Or should it have preserved what 
> > run level settings were previously in effect prior to the update?

Assuming they were disabled with 'chkconfig ... off' and not 'chkconfig --del ...',

Comment 1 Tim Burke 2008-03-17 16:27:00 EDT
Tim Burke (tburke@redhat.com) said: 
> > I would imagine that if all `yum update` does is remove the old pkg and put 
> > in a new one, that these manual config changes I did would be lost and the 
> > default behavior is restored.  Is that correct?  I wasn't sure if there was 
> > any "smarts" in the update process to preserve config settings.

on/off state should not be changed on package updates, assuming it's
'off' as opposed to 'not set up'.

Comment 2 RHEL Product and Program Management 2008-06-02 16:13:28 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 7 errata-xmlrpc 2009-01-20 16:28:47 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.