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.

seems like we should track this change for 3.1 downstream as well

+++ This bug was initially created as a clone of Bug #842775 +++

upgrading from engine will fail to complete the upgrade due to missing grub2 support in ovirt-config-boot. Solution is to change upgrade process to use the newer python scripts from ovirtnode

assuming the iso is mounted at /live all you need to do is:

from ovirtnode.install import *
install = Install()
install.ovirt_boot_setup()

--- Additional comment from juan.hernandez on 2012-07-24 11:05:27 EDT ---

The problem appears when trying to update the node from the engine. This invokes the /usr/share/vdsm-reg/vdsm-upgrade script, and this calls /usr/libexec/ovirt-config-boot passing the mount point of the .iso as the first parameter. The result is the following:

[root@h0 admin]# /usr/share/vdsm-reg/vdsm-upgrade
<BSTRAP component='setMountPoint' status='OK' message='Mount succeeded.'/>
<BSTRAP component='doUpgrade' status='FAIL' message='boot loader install
failed. '/>
<BSTRAP component='umount' status='OK' message='umount Succeeded'/>
<BSTRAP component='RHEV_INSTALL' status='FAIL'/>

need to verify this does not break rhev-h 6.3/3.0 upgrades

As reference: Upstream patch (in review at moment): http://gerrit.ovirt.org/#/c/7074/

Thanks Juan! Yaniv please ignore my comment#3 (for downstream), it's related to a different bug. The patches for this bug is waiting for review in upstream: http://gerrit.ovirt.org/#/c/7074/

Thanks!

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html