Red Hat Bugzilla – Bug 668395
Kickstart network command doesn't reconfigure active connection (unlike in rhel 5).
Last modified: 2011-05-19 08:36:49 EDT
Description of problem:
In RHEL 5, first kickstart network command reactivated active network device with new configuration. In RHEL 6.0 it doesn't.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install using kickstart from network, set network configuration on cmdline.
2. In kickstart have network command for the device activated/used to get kicktart with different configuration.
After kickstart is fetched the configuration from kickstart is not applied.
You can check with ifconfig on tty2 when available.
The configuration from kickstart file is applied and the device is reconfigured after fetching kickstart.
*** Bug 666536 has been marked as a duplicate of this bug. ***
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 release.
This should be fixed in anaconda-13.21.92-1.
With anaconda-13.21.107-1.el6 the network configuration from ks.cfg was applied on top of the previous configuration passed on the command line. Moving to VERIFIED.
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.