|Summary:||Waiting for activation of devices *not* selected before running nm-c-e.|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Radek Vykydal <rvykydal>|
|Component:||anaconda||Assignee:||Radek Vykydal <rvykydal>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Release Test Team <release-test-team>|
|Fixed In Version:||anaconda-13.21.51-1||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-11-10 19:46:30 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Radek Vykydal 2010-06-01 11:57:11 UTC
Created attachment 418606 [details] patch with fix Description of problem: When doing [Configure Network] in anaconda GUI having more than one network device, user selects in a dialog which devices should be configured by NM (edited in nm-c-e). If he unchecks a device that was already set as ONBOOT=yes (e.g. it was used during install, or [ ] Connect Automatically was checked in previous run of nm-c-e), anaconda waits to activation of the device after nm-c-e is left and fails after timeout. It shouldn't wait. Version-Release number of selected component (if applicable): anaconda-13.21.48-1 How reproducible: Always Steps to Reproduce: 1. Install on a machine with 2 network devices (say eth0, eth1). 2. Enable eth0 in stage 1 (e.g. have ks or stage2 or updates.img over network) 2. Run [Configure Networking] in GUI. 3. In pre nm-c-e dialog, check eth1 and uncheck eth0. (This will bring down eth0) 4. Leave nm-c-e, anaconda will wait for activation of eth0 for about 45 s and then error message appears. Actual results: Anaconda waits for eth0 activation. Expected results: Anaconda doesn't wait for eth0 activation as it is not NM controlled. Additional info: Patch attached.
Comment 1 RHEL Product and Program Management 2010-06-01 12:16:02 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Comment 2 Radek Vykydal 2010-06-14 15:41:07 UTC
This should be fixed in anaconda-13.21.51-1.
Comment 4 Alexander Todorov 2010-07-07 15:53:54 UTC
I've tested this with snapshot #7 (0701.3 tree) with 2 NICs. 1) In loader activate eth0 to download stage2. 2) In stage2 press the Configure network button. Since all interfaces are now managed by NM there's no dialog to select which ones will be not. 3) In nm-c-e dialog I've selected eth0 and disabled "Connect automatically". Then selected eth1 and enabled "Connect automatically". This is the closest to "check eth1 and uncheck eth0" 4) Close nm-c-e and swith to tty2 and run ifconfig. It showed that both interfaces were active and had assigned addresses by DHCP. 5) Click Next and proceed with the install. Anaconda didn't wait 45 secods but proceeded right away with the installation. After install the system booted and eth0 was down and eth1 was up as configured in NM. Moving to VERIFIED.
Comment 5 firstname.lastname@example.org 2010-11-10 19:46:30 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.