Bug 668395 - Kickstart network command doesn't reconfigure active connection (unlike in rhel 5).
Summary: Kickstart network command doesn't reconfigure active connection (unlike in rh...
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Keywords:
: 666536 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-10 12:09 UTC by Radek Vykydal
Modified: 2018-11-14 15:51 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2011-05-19 12:36:49 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0530 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-05-18 17:44:52 UTC

Description Radek Vykydal 2011-01-10 12:09:08 UTC 
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):

RHEL 6.0

How reproducible:

always

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.
  
Actual results:

After kickstart is fetched the configuration from kickstart is not applied.
You can check with ifconfig on tty2 when available.

Expected results:

The configuration from kickstart file is applied and the device is reconfigured after fetching kickstart.

Additional info:
Comment 2 Radek Vykydal 2011-01-12 09:04:05 UTC 
*** Bug 666536 has been marked as a duplicate of this bug. ***
Comment 4 RHEL Product and Program Management 2011-01-19 15:30:24 UTC 
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.
Comment 5 Radek Vykydal 2011-01-26 13:41:27 UTC 
This should be fixed in anaconda-13.21.92-1.
Comment 7 Alexander Todorov 2011-03-30 09:52:32 UTC 
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.
Comment 8 errata-xmlrpc 2011-05-19 12:36:49 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2011-0530.html
Note You need to log in before you can comment on or make changes to this bug.