RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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.

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?

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.

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)