Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMatthew Galgoci
2014-05-22 20:53:18 UTC
Created attachment 898493[details]
output of dmidecode from RHEL5.10 installed system.
Description of problem:
I am trying to PXE boot a remote server and do a manual network install (without kickstart). The kernel and initrd load, and it gets to "reached the target Basic System", sits there for what seems like a few minutes, and then drops to the dracut shell.
Version-Release number of selected component (if applicable):
RHEL-7.0-20140507.0-Server-x86_64-dvd1
How reproducible:
100% of the time on this hardware.
Steps to Reproduce:
1. PXE boot kernel and initrd
2.
3.
Actual results:
Dropped to dracut emergency shell.
Expected results:
Installer starts and prompts for network configuration, at which point I would expect to point the installer to a network tree available over http.
Additional info:
I have also tried RHEL6.5 with different results leading up to the failure. Safe to say RHEL6.5 does not make it to anaconda stage 2 and I will file a report for that.
I managed to successfully install RHEL5.10 on this hardware. I have a dmidecode output that I am going to attach in addition to the rdsosreport.txt from RHEL7RC3.
Also note: I spoke with David Cantrell about this, so he is cursorily familiar with the issue. The hardware is internal, but it is a new deployment of HP gear for the "cloud management business unit" - herein referred to as CMBU. We will have the ability to test in the future since this is a lab. I suspect the CMBU folks will jump all over these bugs once they realize they can only get RHEL5.10 installed.
[ 0.000000] localhost kernel: Command line: initrd=rhel7/initrd.img BOOT_IMAGE=rhel7/vmlinuz
I doubt, that's enough parameters to start an installation.
reassigning to anaconda
Created attachment 898493 [details] output of dmidecode from RHEL5.10 installed system. Description of problem: I am trying to PXE boot a remote server and do a manual network install (without kickstart). The kernel and initrd load, and it gets to "reached the target Basic System", sits there for what seems like a few minutes, and then drops to the dracut shell. Version-Release number of selected component (if applicable): RHEL-7.0-20140507.0-Server-x86_64-dvd1 How reproducible: 100% of the time on this hardware. Steps to Reproduce: 1. PXE boot kernel and initrd 2. 3. Actual results: Dropped to dracut emergency shell. Expected results: Installer starts and prompts for network configuration, at which point I would expect to point the installer to a network tree available over http. Additional info: I have also tried RHEL6.5 with different results leading up to the failure. Safe to say RHEL6.5 does not make it to anaconda stage 2 and I will file a report for that. I managed to successfully install RHEL5.10 on this hardware. I have a dmidecode output that I am going to attach in addition to the rdsosreport.txt from RHEL7RC3. Also note: I spoke with David Cantrell about this, so he is cursorily familiar with the issue. The hardware is internal, but it is a new deployment of HP gear for the "cloud management business unit" - herein referred to as CMBU. We will have the ability to test in the future since this is a lab. I suspect the CMBU folks will jump all over these bugs once they realize they can only get RHEL5.10 installed.