Bug 837443 - ovirt-node fails to register with ovirt-engine
Summary: ovirt-node fails to register with ovirt-engine
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Haim
URL:
Whiteboard: infra
: 837868 (view as bug list)
Depends On:
Blocks: 822145 832517 832539
TreeView+ depends on / blocked
 
Reported: 2012-07-03 21:57 UTC by Mike Burns
Modified: 2014-01-13 00:52 UTC (History)
9 users (show)

Fixed In Version: vdsm-4.10.0-5.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-18 14:14:48 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)
vdsm-reg.log (3.07 MB, text/plain)
2012-07-03 21:57 UTC, Mike Burns 		no flags Details
View All

Description Mike Burns 2012-07-03 21:57:41 UTC 
Created attachment 596104 [details]
vdsm-reg.log

Description of problem:
During registration process, vdsm-reg reports an error when trying to register to ovirt-engine

Version-Release number of selected component (if applicable):
ovirt node 2.4.0 + patches (image is available in nightly releases on ovirt.org)
vdsm commit bd164e417c83f02f49a7002c0e6c6997b2f19ce8 + patch set 2 of patch 5600 on gerrit.ovirt.org

How reproducible:
always

Steps to Reproduce:
1.install ovirt-node
2.configure network
3.configure engine setup
  
Actual results:
fails

err=Traceback (most recent call last):
  File "/usr/share/vdsm/configNetwork.py", line 1197, in <module>
  File "/usr/share/vdsm/configNetwork.py", line 1172, in main
  File "/usr/share/vdsm/configNetwork.py", line 736, in delNetwork
ConfigNetworkError: (27, "Cannot delete network 'breth0': It doesn't exist")

ret=27


Expected results:
Host registers correctly

Additional info:
Comment 1 Douglas Schilling Landgraf 2012-07-04 04:06:21 UTC 
Patch available to review:
http://gerrit.ovirt.org/#/c/5914/
Comment 2 Douglas Schilling Landgraf 2012-07-09 20:49:14 UTC 
*** Bug 837868 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.