Bug 1219811 - Though RHEVH upgrade fail, still write "Upgraded Succeeded. Rebooting".
Summary: Though RHEVH upgrade fail, still write "Upgraded Succeeded. Rebooting".
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.5.3
Assignee: Douglas Schilling Landgraf
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On: 1182089
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-08 10:47 UTC by rhev-integ
Modified: 2016-02-10 20:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the return validation of the upgrade script in Red Hat Enterprise Virtualization Hypervisor was not accurate, causing the Red Hat Enterprise Virtualization Manager to report that the RHEV-H upgrade occurred correctly even when it failed. The error has now been fixed, and RHEV-M now shows the correct status of the RHEV-H upgrade. Note that this fix is included in Red Hat Enterprise Virtualization Hypervisor 7.1 images only.
Clone Of: 1182089
Environment:
Last Closed: 2015-06-15 13:20:36 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:
ylavi: Triaged+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1101 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.5.3 2015-06-15 17:20:01 UTC
oVirt gerrit 36921 0 master MERGED ovirt-node-upgrade: set ret statement correctly Never
oVirt gerrit 40618 0 ovirt-3.5 MERGED ovirt-node-upgrade: set ret statement correctly Never

Comment 2 wanghui 2015-05-21 06:20:40 UTC 
Test vesion:
rhev-hypervisor7-7.0-20141218.0 
rhev-hypervisor-7-7.1-20150520.0
ovirt-node-3.2.3-2.el7.noarch
Red Hat Enterprise Virtualization Manager Version: 3.5.3-0.2.el6ev

Test steps:
1. Install rhev-hypervisor7-7.0-20141218.0 
2. Register to rhevm3.5.3-0.2.el6ev
3. Upgrade to rhev-hypervisor-7-7.1-20150520.0 through rhevm3.5.3.
4. Check the events in rhevm.

Test result:
1. Upgrade is not succeed.
2. The events in rhevm portal reports upgraded succeed as follows.
	
2015-May-21, 14:11 Host dhcp-9-197.nay.redhat.com is not responding. It will stay in Connecting state for a grace period of 60 seconds and after that an attempt to fence the host will be issued. 
	
2015-May-21, 14:06 Host dhcp-9-197.nay.redhat.com installed 

2015-May-21, 14:06 Installing Host dhcp-9-197.nay.redhat.com. Step: RHEV_INSTALL.

2015-May-21, 14:06 Installing Host dhcp-9-197.nay.redhat.com. Step: ovirt-node-upgrade; Details: Upgraded Succeeded. Rebooting .

So this issue is not fixed in rhev-hypervisor-7-7.1-20150520.0. Change the status from ON_QA to Assigned.
Comment 3 Douglas Schilling Landgraf 2015-05-21 14:20:11 UTC 
(In reply to wanghui from comment #2)
> Test vesion:
> rhev-hypervisor7-7.0-20141218.0 
> rhev-hypervisor-7-7.1-20150520.0
> ovirt-node-3.2.3-2.el7.noarch
> Red Hat Enterprise Virtualization Manager Version: 3.5.3-0.2.el6ev
> 
> Test steps:
> 1. Install rhev-hypervisor7-7.0-20141218.0 
> 2. Register to rhevm3.5.3-0.2.el6ev
> 3. Upgrade to rhev-hypervisor-7-7.1-20150520.0 through rhevm3.5.3.
> 4. Check the events in rhevm.
> 
> Test result:
> 1. Upgrade is not succeed.
> 2. The events in rhevm portal reports upgraded succeed as follows.
> 	
> 2015-May-21, 14:11 Host dhcp-9-197.nay.redhat.com is not responding. It will
> stay in Connecting state for a grace period of 60 seconds and after that an
> attempt to fence the host will be issued. 
> 	
> 2015-May-21, 14:06 Host dhcp-9-197.nay.redhat.com installed 
> 
> 2015-May-21, 14:06 Installing Host dhcp-9-197.nay.redhat.com. Step:
> RHEV_INSTALL.
> 
> 2015-May-21, 14:06 Installing Host dhcp-9-197.nay.redhat.com. Step:
> ovirt-node-upgrade; Details: Upgraded Succeeded. Rebooting .
> 
> So this issue is not fixed in rhev-hypervisor-7-7.1-20150520.0. Change the
> status from ON_QA to Assigned.

Actually, the patch is included in this ISO and should be fixing this bug. However, you cannot test upgrading from rhev-hypervisor7-7.0-20141218.0  to rhev-hypervisor-7-7.1-20150520.0 because the 7.0 doesn't include the fix in ovirt-node-upgrade tool. So even upgrading to image that contain the fix doesn't. At moment, the best way to test it is upgrading rhev-hypervisor-7-7.1-20150520.0 to itself or with a higher version. As soon you confirm please remove the flag FailedQA
Comment 4 wanghui 2015-05-22 02:48:41 UTC 
As comment#3 said, this issue need to be tested to upgrading rhev-hypervisor-7-7.1-20150520.0 to itself. So test this issue as follows.

Test vesion: 
rhev-hypervisor-7-7.1-20150520.0
ovirt-node-3.2.3-2.el7.noarch
Red Hat Enterprise Virtualization Manager Version: 3.5.3-0.2.el6ev

Test steps:
1. Install rhev-hypervisor-7-7.1-20150520.0
2. Register to rhevm3.5.3-0.2.el6ev
3. Change add a quota in MANAGED_BY field as follows.
   MANAGED_BY=""RHEV-M https://10.66.111.73:443""
4. Persist /etc/default/ovirt
5. Upgrade to rhev-hypervisor-7-7.1-20150520.0 through rhevm3.5.3.
6. Check the events in rhevm.

Test result:
1. Upgrade is not succeed.
2. The events in rhevm portal reports upgraded failed as follows.

2015-May-22, 10:42 Host dhcp-10-41.nay.redhat.com installation failed. Upgrade failed, please refer to logs for further information.

2015-May-22, 10:42 Failed to install Host dhcp-10-41.nay.redhat.com. Step: RHEV_INSTALL.

2015-May-22, 10:42 Failed to install Host dhcp-10-41.nay.redhat.com. Step: ovirt-node-upgrade; Details: Upgraded Failed .

So this issue is fixed in rhev-hypervisor-7-7.1-20150520.0. Change the status from ON_QA to Verified.
Comment 8 errata-xmlrpc 2015-06-15 13:20:36 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-1101.html
Note You need to log in before you can comment on or make changes to this bug.