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:
RHEVH show no response status in RHEV-M after upgrade from 6.3GA to latest6.4 with UEFI machine.


Failed to install Host dell-per510-01.qe.lab.eng.nay.redhat.com. Step: RHEV_INSTALL.
Host dell-per510-01.qe.lab.eng.nay.redhat.com installation failed. SSH command failed while executing at host '10.66.110.242', refer to logs for further information.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130227.0.el6_4
Si27.2

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H 6.3GA(rhev-hypervisor6-6.3-20121121.0.el6_3) and register to rhevm Si27.2
2. Approve the host.
3. Maintenance the host.
4. Upgrade the host to rhev-hypervisor6-6.4-20130227.0.el6_4.

Actual results:
1. RHEVH show no response status in RHEV-M
2. RHEV-H not reboot.
3. RHEV-H can upgrade successful via cmd.
4. No such issue in legacy machine.

Expected results:
RHEVH shows up in RHEVM after upgrade finished and the host rebooted.

Additional info:

Created attachment 703829 [details]
engine.log

Created attachment 703830 [details]
vdsm.log

Created attachment 704089 [details]
rhevm.log

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

*** This bug has been marked as a duplicate of bug 867562 ***