Bug 609706 - Network Error
Network Error
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
6.1
All Linux
low Severity medium
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-30 16:48 EDT by Mike McGrath
Modified: 2010-07-01 11:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-01 11:42:23 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)
syslog of the install error (14.38 KB, application/x-gzip)
2010-06-30 19:24 EDT, Mike McGrath
no flags Details

  None (edit)
Description Mike McGrath 2010-06-30 16:48:11 EDT
Description of problem:

I've got an IBM X series M/T - 794772U that, upon boot throws a network error making unattended reinstalls impossible.

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

Whatever ships with the RHEL6 beta 2 today


How reproducible:

Every time.



Steps to Reproduce:
1. Boot with the following appended parameters:
2. ks initrd=images/RHEL/6/x86_64/initrd.img ksdevice=eth0 ip=dhcp console=ttyS0,115200n8 method=blah ks=blah
  
Actual results:

Anaconda stops with a prompt "Network Error" and the console button is "Retry".  Upon clicking retry and selecing eth0, everything boots fine.

Expected results:

It shouldn't throw an error.

Additional info:
Comment 2 RHEL Product and Program Management 2010-06-30 17:03:15 EDT
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 3 Chris Lumens 2010-06-30 17:06:04 EDT
Is there any way you can get in front of this machine, or is it serial console access only?  If the former, can you attach a screenshot of tty3 and tty4?  If the latter, can you hit the error, proceed to stage2, and then pull /tmp/syslog off and attach to this bug?
Comment 4 Mike McGrath 2010-06-30 19:24:37 EDT
Created attachment 428138 [details]
syslog of the install error

I might be able to get the other TTY's but this is a new host and the remote management card is busted, I've contacted the vendor and they are shipping one overnight.  If the syslog doesn't tell enough of the story, it might be a bit but I think I can get the other ttys.
Comment 5 Mike McGrath 2010-07-01 11:42:23 EDT
Ugh, this was a tree failure on my part (I was testing against beta 1, beta 2 doesn't do this anymore.  Sorry for the noise)

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