Bug 1051136 - uefi iscsi upgrade failure
Summary: uefi iscsi upgrade failure
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.5.2
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On: 885987
Blocks: 520111 rhevh-software-iscsi-root
TreeView+ depends on / blocked
 
Reported: 2014-01-09 18:24 UTC by Joey Boggs
Modified: 2016-02-10 20:03 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 885987
Environment:
Last Closed: 2015-03-05 10:56:14 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Fabian Deutsch 2014-07-24 16:02:47 UTC
This is a mass change, moving bugs of merged patches into MODIFIED.

Please correct the state, if you think that the move was not justified.

Comment 3 haiyang,dong 2014-11-18 12:51:11 UTC
Test version:
rhev-hypervisor6-6.6-20141107.0.iso
ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el6.noarch

Test cases in uefi machine:
(a) Support rhev-h upgrade via ovirt-node-upgrade tools in uefi mode machine after enabled iscsi boot----PASS.

(b) Support rhev-h upgrade via cmdline in uefi mode machine after enabled iscsi boot----FAIL 
Failed in finding logging devices
----------
Enable Networking
------------------------
Checking pre-conditions...
(1/1) Configuring network

All changes were applied successfully.

Trackback (most recent call last):
File "<stdin>", line3, in <module>
File "/usr/lib/python2.6/site-packages/ovirtnode/install.py", line 670, in ovirt_boot_setup
File "/usr/lib/python2.6/site-packages/ovirtnode/ovirtfunctions.py", line 1180
in finish_install
Assertion Error:Failed to find logging devices.

(c) Support rhev-h upgrade via TUI in uefi mode machine after enabled iscsi boot--- FAIL (It will enter into install process page, not upgrade process page)

so need re-assigned this bug again


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