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']
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.
(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.
(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/ ?
or http://fedorapeople.org/groups/virt/virt-preview/fedora-19/rpms/ ?
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.
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']
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released