Bug 1260559 - Upgrade rhev-h from 7.1 to 7.2 via TUI failed - hang
Summary: Upgrade rhev-h from 7.1 to 7.2 via TUI failed - hang
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-3.6.1
: 3.6.0
Assignee: Ryan Barry
QA Contact: cshao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-07 09:02 UTC by cshao
Modified: 2016-03-09 14:37 UTC (History)
11 users (show)

Fixed In Version: ovirt-node-3.6.1-5.0.el7ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 14:37:09 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
TUI-failed.png (20.35 KB, image/jpeg)
2015-09-07 09:02 UTC, cshao
no flags Details
/var/log/*.* (134.46 KB, application/x-gzip)
2015-09-08 06:10 UTC, cshao
no flags Details
failed-tui-new.png (674.96 KB, image/png)
2015-09-08 06:11 UTC, cshao
no flags Details
drop to shell (9.67 KB, image/png)
2015-10-26 08:42 UTC, cshao
no flags Details
upgrade_tui_1025 (5.29 MB, application/x-gzip)
2015-10-26 08:44 UTC, cshao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0378 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.6 2016-03-09 19:06:36 UTC
oVirt gerrit 46043 0 master MERGED Move initramfs regeneration until after grub is installed Never
oVirt gerrit 46105 0 ovirt-3.6 MERGED Move initramfs regeneration until after grub is installed Never

Description cshao 2015-09-07 09:02:56 UTC
Created attachment 1070869 [details]
TUI-failed.png

Description of problem:
Upgrade rhev-h from 7.1 to 7.2 via TUI failed. 

Due to the upgrade process always hung on some location like attachment show, so I can't obtain any log info.

I have to separate the upgrade issue into three bugs, because all of them has different result, Thanks for understanding. 


Version-Release number of selected component (if applicable):
rhev-hypervisor-7-7.1-20150827.1
rhev-hypervisor-7-7.2-20150831.0
ovirt-node-3.3.0-0.2.20150722git7eba125.el7ev.noarch
vdsm-4.17.3-1.el7ev.noarch
RHEV-M vt16.9
Red Hat Enterprise Virtualization Manager Version: 3.5.4-1.3.el6ev

How reproducible:
100%

Steps to Reproduce:
1. Install rhevh 7.1 3.5.4GA build(rhev-hypervisor-7-7.1-20150827.1).
2. Upgrade via TUI


Test result:
1. Upgrade failed, it always hung on some location like attachment show.

Expected results:
Upgrade rhev-h from 7.1 to 7.2 via TUI can successful.

Additional info:

Comment 2 Fabian Deutsch 2015-09-07 09:56:13 UTC
Chen, the picture looks like the host was rebooted.
Was this picture taken after the host reboot?

Comment 3 cshao 2015-09-07 10:08:48 UTC
(In reply to Fabian Deutsch from comment #2)
> Chen, the picture looks like the host was rebooted.
> Was this picture taken after the host reboot?

No, the picture taken after enter pxe. and it will not enter upgrading process.

1. Install rhevh 7.1 3.5.4GA build(rhev-hypervisor-7-7.1-20150827.1).
2. Reboot 7.1
3. Boot from PXE.
4. Move to 7.2 profile, and press "Enter" key.

Then the bug occurs.

Thanks!

Comment 4 Fabian Deutsch 2015-09-07 12:28:50 UTC
Could you please retry, and remove the quiet and rhgb keywords on the kernel cmdline.

Comment 5 cshao 2015-09-08 06:09:37 UTC
(In reply to Fabian Deutsch from comment #4)
> Could you please retry, and remove the quiet and rhgb keywords on the kernel
> cmdline.

After remove the quiet and rhgb keywords on the kernel cmdline, I can enter into the upgrading process now, but still got failed(Exception: RuntimeError('Failed to set install bootloader'.))

This time I can obtain some log info and paste in here for your reference.
/var/log/*.*

Thanks!

Comment 6 cshao 2015-09-08 06:10:28 UTC
Created attachment 1071201 [details]
/var/log/*.*

Comment 7 cshao 2015-09-08 06:11:08 UTC
Created attachment 1071202 [details]
failed-tui-new.png

Comment 9 cshao 2015-10-26 08:41:26 UTC
I have to assigned this bug due met below error.

Test version:
rhev-hypervisor-7-7.1-20150827.1
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch

Test steps:
1. Install rhevh 7.1 3.5.4GA build(rhev-hypervisor-7-7.1-20150827.1).
2. Reboot 7.1
3. Boot from PXE.
4. Move to 7.2-1025 profile, and press "Enter" key.
5. Finish the installation process with correct steps.
6. Reboot host
7. Try to enter 7.2 host.

Test result:
Step1-6: Pass
Step7: An error occurs in the UI: IOError(2, ‘No such file or directory’)
Press ENTER to logout
or enter 's' to drop to shell

Please see attachment for more details.

Comment 10 cshao 2015-10-26 08:42:10 UTC
Created attachment 1086412 [details]
drop to shell

Comment 11 cshao 2015-10-26 08:44:05 UTC
Created attachment 1086413 [details]
upgrade_tui_1025

Comment 12 Ryan Barry 2015-10-27 02:39:10 UTC
(In reply to shaochen from comment #9)
> I have to assigned this bug due met below error.
> 
> Test version:
> rhev-hypervisor-7-7.1-20150827.1
> rhev-hypervisor7-7.2-20151025.0.el7ev
> ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch
> 
> Test steps:
> 1. Install rhevh 7.1 3.5.4GA build(rhev-hypervisor-7-7.1-20150827.1).
> 2. Reboot 7.1
> 3. Boot from PXE.
> 4. Move to 7.2-1025 profile, and press "Enter" key.
> 5. Finish the installation process with correct steps.
> 6. Reboot host
> 7. Try to enter 7.2 host.
> 
> Test result:
> Step1-6: Pass
> Step7: An error occurs in the UI: IOError(2, ‘No such file or directory’)
> Press ENTER to logout
> or enter 's' to drop to shell
> 
> Please see attachment for more details.

This is almost certainly a new/different bug which is unrelated to the previous comments in this bug.

Was the system able to be upgraded? The logs look like /live failed to mount in the installer (/live/syslinux/version cannot be read), but there are messages from ovirt.node.setup further down.

I'll try to reproduce this tomorrow

Comment 13 cshao 2015-10-27 03:11:05 UTC
> This is almost certainly a new/different bug which is unrelated to the
> previous comments in this bug.

Seems they are different issue. so can I verify this bug and then report a new one?


> Was the system able to be upgraded? 
Yes, the system was able to be upgraded, and the new issue occurs after upgrade.

> The logs look like /live failed to mount
> in the installer (/live/syslinux/version cannot be read), but there are
> messages from ovirt.node.setup further down.
> 
> I'll try to reproduce this tomorrow

Thanks!

Comment 14 cshao 2015-10-28 08:36:40 UTC
VERIFY this bug according #c12-13  & bug 1260551#c7.

And the new bug is here:
Bug 1275956 - In Boot process show IOError info when upgrade via TUI/AUTO/RHEVM

Test version:
rhev-hypervisor-7-7.1-20150827.1
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch

Test steps:
1. Install rhevh 7.1 3.5.4GA build(rhev-hypervisor-7-7.1-20150827.1).
2. Reboot 7.1
3. Boot from PXE.
4. Move to 7.2-1025 profile, and press "Enter" key.
5. Finish the installation process with correct steps.
6. Reboot host

Test result:
The system was able to be upgraded without hang.

Comment 16 errata-xmlrpc 2016-03-09 14:37:09 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-2016-0378.html


Note You need to log in before you can comment on or make changes to this bug.