Bug 594499 - Anaconda bad handling of second ethernet adapter
Anaconda bad handling of second ethernet adapter
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
12
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-20 16:43 EDT by Raman Gupta
Modified: 2010-05-25 15:50 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 15:50:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Raman Gupta 2010-05-20 16:43:02 EDT
Description of problem:

I have two ethernet adapters, eth0 and eth1. The first is the built-in
motherboard adapter which I don't use (nothing is plugged in) and the second is
an Intel gigabit add-on controller card.

I have nothing plugged into eth0. My network is plugged into eth1.

During the anaconda fresh net install (not an upgrade), it was able to download
the stage2 image but once it got to the point of connecting to a yum repository
it failed -- the network connection was unavailable.

I was able to continue by switching to another virtual console and manually
doing:

ip route flush all
ip route add 192.168.1.0/24 dev eth1
ip route add default via 192.168.1.1

At this point the network routed via the correct adapter, all was well, and I
was able to continue the anaconda install.
Comment 1 Chris Lumens 2010-05-25 00:15:55 EDT
Please attach /tmp/anaconda.log and /tmp/syslog from the point when you hit this problem to this bug report.
Comment 2 Raman Gupta 2010-05-25 15:33:32 EDT
Unfortunately, they have been removed by tmpwatch.

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