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.

Description of problem:

We are upgrading deployed servers from RHEL 5 to RHEL 6. To do this we are upgrading using a kickstart file and updating the grub config of the RHEL 5 server so that after restart the kickstart upgrade kicks in. The kickstart file is specifying the URL of the FTP server hosting the RHEL 6 image for install. After reboot, the upgrade is failing to connect to the FTP server. If we manually issue a retry, the installation continues successfully. 

We were able to issue the retry because we had an HP iLO interface configured on the server. But if we did not have that interface, the system would be in a state that would require us to go onsite to manually restart the box. 

There was no indication as to why the initial attempt to connect to the FTP server failed. It is in a reliable intranet, so there should be no connectivity issue.


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


How reproducible:
Happened once at one customer site. Did not happen at many other upgrade sites.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Please attach the kickstart file you are using as well as the log files from the /tmp directory in the install environment.  Attach the files as individual plain text files to this bug report.

Created attachment 672430 [details]
kickstart file

There are no relevent log file sin the /tmp directory. Is there is a specific file that you are looking for.

/tmp/syslog and /tmp/anaconda.log would be helpful.  Note that these must be grabbed while in the installation environment.  They will not be available after rebooting.

This info is no longer available. The system that this issue occured on was a production system and, as I mentioned in the description problem, we were able to progress the remote installation forward by using the HP iLO interface.

Since we eventually upgraded the system (including reboot) this info is no longer available.