Bug 230975 - Anaconda hangs on IBM ppc blades using eth1 as ethernet connection during setup
Summary: Anaconda hangs on IBM ppc blades using eth1 as ethernet connection during setup
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: ppc64 Linux
Target Milestone: ---
Assignee: David Cantrell
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-05 08:28 UTC by Jerone Young
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-26 20:04:26 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jerone Young 2007-03-05 08:28:22 UTC
Description of problem:
  A JS20 blade in a blade center. These JS20 must use the 2nd ethernet card
(eth1) for connecting to the outside world. The first ethernet card (eth0) is
not used is meant for communications within the blade center.

Version-Release number of selected component (if applicable):

How reproducible:
 You netboot the install image using the 2nd ethernet device. You tell the
install image to use the 2nd ethernet device (eth1). Now point to the repo where
install files are and start the setup.

 While going through the setup. After you partitioning the disk. You are
prompted to setup the ethernet settings. These ethernet settings are for eth0.
Now we don't use eth0 so you tell it not to activate it on boot. And you have to
say that it will use IP4 and choose weather it's DHCP or Manual.
  After going through this the next screen never comes up. I would assume it
would be to setup eth1 (the interface we use). But nothing ever comes up and it
is just stuck. Hung.
  So you cannot finish your install on a JS20 blade. Meaning no way to install.

Comment 1 Jerone Young 2007-03-06 23:18:47 UTC
This problem appears to only effect the text installer through a serial console.
Using the VNC to get to the GUI installer it works fine.

Comment 2 David Cantrell 2007-03-26 16:05:21 UTC
I recently updated the network configuration stages in the text mode installer
to reflect how the GUI mode installer works.  Can you try a recent rawhide to
see if the problem still occurs?

Comment 3 Jerone Young 2007-03-26 20:04:26 UTC
This solved the problem. Now can get through menu without issue. It's all a
nicer way to configure interfaces.

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