Bug 999461 - SetupNetworks fails during host installation
Summary: SetupNetworks fails during host installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.3.0
Assignee: Mike Kolesnik
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 11:09 UTC by Moti Asayag
Modified: 2016-02-10 19:48 UTC (History)
8 users (show)

Fixed In Version: is13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:18:52 UTC
oVirt Team: Network
Target Upstream Version:


Attachments (Terms of Use)
vdsm log (1.51 MB, text/plain)
2013-08-21 11:09 UTC, Moti Asayag
no flags Details
supervdsm log (898 bytes, text/plain)
2013-08-21 11:10 UTC, Moti Asayag
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 18683 0 None None None Never
oVirt gerrit 18785 0 None None None Never

Description Moti Asayag 2013-08-21 11:09:24 UTC
Created attachment 788819 [details]
vdsm log

Description of problem:
On fresh rhel-6.4 installation, the setup networks fails since the supervdsm service isn't ready to accept requests.

Version-Release number of selected component (if applicable):
vdsm-4.10.2-23.0.el6ev.x86_64

How reproducible:
not always.

Steps to Reproduce:
1. Add new host to 3.2 cluster (the destination vdsm should be 3.2 as well)

Actual results:
Creating the management network using setupNetworks fails due to:
AttributeError: 'ProxyCaller' object has no attribute 'setupNetworks'
(the entire log is attached)

Expected results:
Management network should be installed properly on the host using setupNetworks.

Additional info:
The supervdsm service isn't ready to accept calls from the vdsm, as appear in the log. It seems the reattempt to send the setupNetworks should succeed.

Comment 1 Moti Asayag 2013-08-21 11:10:08 UTC
Created attachment 788820 [details]
supervdsm log

Comment 2 Moti Asayag 2013-08-29 09:17:06 UTC
A specific scenario should be tested with this fix:

Installing ovirt-node-3.3 into a 3.2 cluster. In ovirt-node 3.3 the pre-created bridge devices (breth*) are no longer created.
There is a need to assure the host deploy creates the management network as a bridge on that node.

Comment 3 Alon Bar-Lev 2013-09-02 13:20:56 UTC
over automation

Comment 4 Martin Pavlik 2013-09-04 13:22:12 UTC
3.3 compatible rhev-h is not available yet

Comment 5 Martin Pavlik 2013-09-12 08:31:16 UTC
verified, RHEV Hypervisor - 6.5 - 20130910.2.el6 (vdsm-4.12.0-127.gitedb88bf.el6ev) properly added in 3.2 cluster on is14

Comment 6 Itamar Heim 2014-01-21 22:18:52 UTC
Closing - RHEV 3.3 Released

Comment 7 Itamar Heim 2014-01-21 22:25:08 UTC
Closing - RHEV 3.3 Released


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