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

Bug 1056918

Summary:	Not able to add a node to 3.4 Cluster in Ovirt 3.4 engine
Product:	[Retired] oVirt	Reporter:	Ramesh N <rnachimu>
Component:	vdsm	Assignee:	Francesco Romani <fromani>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.4	CC:	acathrow, bazulay, bugs, danken, didi, gklein, iheim, josh, lnatapov, mgoldboi, sbonazzo, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.4.0-beta2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-31 12:26:59 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 Ramesh N 2014-01-23 07:30:28 UTC

Description of problem:

Note able to add a node to 3.4 Cluster in Ovirt 3.4 engine. 

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

How reproducible:
Always

Steps to Reproduce:
1. Install vdsm 3.4 using the repo http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/

2. Add the above node to a 3.4 Cluster

Actual results:

  Installation succeeds, but node goes to non operational with the error "Host 10.70.43.160 is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.4.". 

Expected results:

  Node should be up and running in 3.4 cluster.


Additional info:

 Repo used to install VDSM:

   http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/

Following is the vdsm version installed in F19 node:

[root@localhost ~]# rpm -qa | grep vdsm
vdsm-cli-4.14.1-2.fc19.noarch
vdsm-4.14.1-2.fc19.x86_64
vdsm-python-4.14.1-2.fc19.x86_64
vdsm-python-zombiereaper-4.14.1-2.fc19.noarch
vdsm-xmlrpc-4.14.1-2.fc19.noarch
vdsm-gluster-4.14.1-2.fc19.noarch

VDS Capability :

[root@localhost ~]# vdsClient -s 0 getVdsCaps
	clusterLevels = ['3.0', '3.1', '3.2', '3.3']

Comment 1 Dan Kenigsberg 2014-01-23 07:59:30 UTC

f19's default libvirt does not support VIR_MIGRATE_ABORT_ON_ERROR which is required for clusterLevel>=3.4.

http://gerrit.ovirt.org/23273

I suppose we can improve the user experience by adding an explicit log line. I do not know if we can do anything else about it.

Comment 2 Sandro Bonazzola 2014-01-23 08:22:37 UTC

(In reply to Dan Kenigsberg from comment #1)
> f19's default libvirt does not support VIR_MIGRATE_ABORT_ON_ERROR which is
> required for clusterLevel>=3.4.
> 
> http://gerrit.ovirt.org/23273
> 
> I suppose we can improve the user experience by adding an explicit log line.
> I do not know if we can do anything else about it.

If nothing will be done on VDSM side, please open a bug against engine-setup for checking vdsm cluster level compatibility while installing all-in-one.

Comment 3 Sandro Bonazzola 2014-01-23 08:28:25 UTC

(In reply to Dan Kenigsberg from comment #1)
> f19's default libvirt does not support VIR_MIGRATE_ABORT_ON_ERROR which is
> required for clusterLevel>=3.4.
> 
> http://gerrit.ovirt.org/23273
> 
> I suppose we can improve the user experience by adding an explicit log line.
> I do not know if we can do anything else about it.

Should we require libvirt from ftp://libvirt.org/libvirt/ ?

Comment 4 Sandro Bonazzola 2014-01-23 08:29:00 UTC

or http://fedorapeople.org/groups/virt/virt-preview/fedora-19/rpms/ ?

Comment 5 Sandro Bonazzola 2014-01-23 08:40:36 UTC

Ramesh, please enable fedora-virt-preview repo, it's delivered with ovirt-release and disaled by default.
Francesco, Danken please ping Fedora people for upgrading libvirt on F19.

Comment 6 Leonid Natapov 2014-02-17 12:32:16 UTC

3.4.0-0.7.beta2.el6. node 3.4 can be added to cluster 3.4.
[root@green-vdsb ~]# vdsClient -s 0 getVdsCaps | grep cluster
	clusterLevels = ['3.0', '3.1', '3.2', '3.3', '3.4']

Comment 7 Sandro Bonazzola 2014-03-31 12:26:59 UTC

this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released