Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 831998

Summary: It's impossible to create bond with setupNetworks
Product: [Retired] oVirt Reporter: GenadiC <gcheresh>
Component: vdsmAssignee: Igor Lvovsky <ilvovsky>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: abaron, acathrow, bazulay, danken, dyasny, fsimonce, iheim, lpeer, mgoldboi, oschreib, ykaul
Target Milestone: ---Keywords: Regression, Reopened, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard: network
Fixed In Version: vdsm-4.10.0-4.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 08:00:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 822145    
Attachments:
Description Flags
vdsm log with the error on creating bond for eth1 and eth3
none
zipped attachement none

Description GenadiC 2012-06-14 09:11:48 UTC 
Created attachment 591780 [details]
vdsm log with the error on creating bond for eth1 and eth3

Description of problem:

Creation of bond fails with Error in setupNetworks.
MainProcess|Thread-472::ERROR::2012-06-14 11:24:25,152::supervdsmServer::76::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks
  File "/usr/share/vdsm/supervdsmServer.py", line 150, in setupNetworks

Version-Release number of selected component (if applicable):


How reproducible:

always
Steps to Reproduce:
1.Use setupNetwork to create a bond
  
Actual results:
GUI is stucked and vdsm reports Error in setupNetworks

Expected results:

Bond should be created
Additional info:
I used the latest rpm's from 14jun build
Comment 1 GenadiC 2012-06-14 11:57:59 UTC 
Created attachment 591818 [details]
zipped attachement
Comment 2 Dan Kenigsberg 2012-06-14 12:59:51 UTC 
> I used the latest rpm's from 14jun build

please use name-version-release, and don't trust our dusty memory when and where we've built an rpm.
Comment 3 GenadiC 2012-06-14 13:21:11 UTC 
(In reply to comment #2)
> > I used the latest rpm's from 14jun build
> 
> please use name-version-release, and don't trust our dusty memory when and
> where we've built an rpm.


Name        : vdsm
Version     : 4.10.0
Release     : 1.fc17
Comment 4 Igor Lvovsky 2012-06-20 11:39:39 UTC 
Fixed in vdsm-4.9.6-17.0.el6
Comment 5 Ofer Schreiber 2012-06-20 11:57:43 UTC 
This bug is on ovirt, and is a blocker for ovirt 3.1 release.
Please provide an Fedora build for it before closing it.
Comment 6 Federico Simoncelli 2012-06-28 22:53:56 UTC 
Fixed in vdsm-4.10.0-4.fc17
Comment 7 Itamar Heim 2012-08-09 08:00:54 UTC 
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/