Bug 948269

Summary:	Registering ovirt-node-2.6.1 fails to register with AIO 1.0
Product:	[Retired] oVirt	Reporter:	Fabian Deutsch <fdeutsch>
Component:	vdsm	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED NOTABUG	QA Contact:	Haim <hateya>
Severity:	unspecified	Docs Contact:
Priority:	urgent
Version:	3.2	CC:	abaron, acathrow, bazulay, dyasny, iheim, mgoldboi, yeylon, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-09 18:15:53 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:

Description Fabian Deutsch 2013-04-04 13:14:50 UTC

Description of problem:
ovirtnode-2.6.1 fails to register with ovirt engine 3.2.1.

But it can be registered to 3.2.0.


Version-Release number of selected component (if applicable):
ovirtnode-2.6.1
ovirt engine 3.2.1.

How reproducible:
always

Steps to Reproduce:
1. Install VM with Node
2. Install a VM with AIO 1.0
3. Node: Setup Net and register to engine
  
Actual results:
Node doesn't appear in engine

Expected results:
Node appears to get approved

Additional info:
As said, 2.6.1 can be registerd to 3.2.0 (tested w/ AIO 0.97)

Comment 1 Fabian Deutsch 2013-04-04 13:18:44 UTC

Early I mentioned that it was engine 3.2.1 - I dunno where I saw this number.

So correcting me: Itw orks with AIO 0.97, but not with AIO 1.0

Comment 2 Dan Kenigsberg 2013-04-05 08:57:18 UTC

If this is indeed a vdsm-reg bug, please supply the exact vdsm version, and as much of vdsm-reg logs that you can find on the node.

Comment 3 Fabian Deutsch 2013-04-09 18:15:53 UTC

False alarm.

I suppose I didn't wait for the refresh the last time.
A fresh 2.6.1 Node could be registered and appeared in Engine.