- Users - oVirt List Archives

[Users] SELinux persistent changes on ovirt node
by Francisco Pérez 23 Jan '14

23 Jan '14

Hi. I have a question regarding to the ovirt node. Im trying to disable o set selinux in permissive mode..I have modified /etc/sysconfig/selinux and then use the persist command on it but sestats output shows the following: [root@ovirth1 ~]# sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: permissive Policy version: 24 Policy from config file: targeted I have found that this also can be acomplished by modifying kernel's boot parameters So it's looks like kernel's boot parameter enforce=1 overrides /etc/sysconfig/selinux. Where is the config file to set enforce=0? Can't find grub config on the node. Best regards Francisco

2 1

[Users] Conflicts during enigne install
by Piotr Kliczewski 23 Jan '14

23 Jan '14

As part of test day I wanted to install engine 3.4.0-0.5.beta1.fc20 from ovirt-3.4.0-prerelease and I can see following info: Transaction check error: file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.py conflicts between attempted installs of ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and sos-3.0-3.fc20.noarch file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.pyc conflicts between attempted installs of ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and sos-3.0-3.fc20.noarch file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.pyo conflicts between attempted installs of ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and sos-3.0-3.fc20.noarc Thanks, Piotr

2 1

[Users] ovirt 3.4 beta on F19: engine-setup error "Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute"
by Jorick Astrego 23 Jan '14

23 Jan '14

Hi, Installing a fresh fedora 19 minimal install and ovirt 3.4 beta got me stuck again. Maybe we should do a bit more QA before releasing a beta? --== CONFIGURATION PREVIEW ==-- Engine database name : engine Engine database secured connection : False Engine database host : localhost Engine database user name : engine Engine database host name validation : False Engine database port : 5432 NFS setup : True PKI organization : xxxxx.xxx Application mode : both Firewall manager : firewalld Update Firewall : True Configure WebSocket Proxy : True Host FQDN : xxxx.xxxxx.xxxxx NFS export ACL : 0.0.0.0/0.0.0.0(rw) NFS mount point : /var/lib/exports/iso Datacenter storage type : posixfs Configure local Engine database : True Set application as default page : True Configure Apache SSL : True Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Initializing PostgreSQL [ INFO ] Creating PostgreSQL 'engine' database [ INFO ] Configuring PostgreSQL [ ERROR ] Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute [ INFO ] Yum Performing yum transaction rollback [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140123145115.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed 2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd systemd.state:134 starting service postgresql 2014-01-23 14:52:35 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:366 execute: ('/bin/systemctl', 'start', 'postgresql.service'), executable='None', cwd='None', env=None 2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:383 execute-result: ('/bin/systemctl', 'start', 'postgresql.service'), rc=1 2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:441 execute-output: ('/bin/systemctl', 'start', 'postgresql.service') stdout: 2014-01-23 14:52:40 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:446 execute-output: ('/bin/systemctl', 'start', 'postgresql.service') stderr: Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details. 2014-01-23 14:52:40 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 182, in _misc self._provisioning.provision() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py", line 552, in provision self._restart() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py", line 407, in _restart state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 138, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 77, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in execute command=args[0], RuntimeError: Command '/bin/systemctl' failed to execute 2014-01-23 14:52:40 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'Yum Transaction' 2014-01-23 14:52:40 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:92 Yum Performing yum transaction rollback Loaded plugins: langpacks, refresh-packagekit, versionlock 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'Database Transaction' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'Version Lock Transaction' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'Firewalld Transaction' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/sysctl.d/ovirt-engine.conf'' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/firewalld/services/ovirt-postgres.xml'' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/firewalld/services/ovirt-https.xml'' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/firewalld/services/ovirt-websocket-proxy.xml'' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/firewalld/services/ovirt-nfs.xml'' 2014-01-23 14:52:40 DEBUG otopi.transaction transaction.abort:131 aborting 'File transaction for '/etc/firewalld/services/ovirt-http.xml'' 2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:456 ENVIRONMENT DUMP - BEGIN 2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:471 ENV BASE/error=bool:'True' 2014-01-23 14:52:40 DEBUG otopi.context context.dumpEnvironment:473 ENVIRONMENT DUMP - END 2014-01-23 14:52:40 INFO otopi.context context.runSequence:395 Stage: Clean up 2014-01-23 14:52:40 DEBUG otopi.context context.runSequence:399 STAGE cleanup Kind regards, Jorick Astrego Netbulae B.V.

4 4

[Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
by Brad House 23 Jan '14

23 Jan '14

I'm trying to test out the oVirt Hosted Engine, but am experiencing a failure early on and was hoping someone could point me in the right direction. I'm not familiar enough with the architecture of oVirt to start to debug this situation. Basically, I run the "hosted-engine --deploy" command and it outputs: ======================== [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140122110741.log Version: otopi-1.2.0_beta (otopi-1.2.0-0.1.beta.fc19) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination ======================== /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140122110741.log has: ======================== 2014-01-22 11:07:57 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-22 11:07:57 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 729, in _customization self._check_existing_pools() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1292, in single_request self.send_content(h, request_body) File "/usr/lib64/python2.7/xmlrpclib.py", line 1439, in send_content connection.endheaders(request_body) File "/usr/lib64/python2.7/httplib.py", line 969, in endheaders self._send_output(message_body) File "/usr/lib64/python2.7/httplib.py", line 829, in _send_output self.send(msg) File "/usr/lib64/python2.7/httplib.py", line 791, in send self.connect() File "/usr/lib64/python2.7/site-packages/vdsm/SecureXMLRPCServer.py", line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File "/usr/lib64/python2.7/socket.py", line 571, in create_connection raise err error: [Errno 111] Connection refused 2014-01-22 11:07:57 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused ======================== Unfortunately I do not know what service this is trying to connect to, or what hostname or port to try to start debugging that. Some other useful information about my environment: - Fedora 19 (64bit), minimal install, selected 'standard' add-on utilities. This was a fresh install just for this test. - 512MB /boot ext4 - 80GB / ext4 in LVM, 220GB free in VG - "yum -y update" performed to get all latest updates - SElinux in permissive mode - Hardware: - Supermicro 1026T-URF barebones - single CPU populated (Xeon E5630 4x2.53GHz) - 12GB ECC DDR3 RAM - H/W Raid with SSDs - Networking: - Network Manager DISABLED - 4 GbE ports (p2p1, p2p2, em1, em2) - all 4 ports configured in a bond (bond0) using balance-alb - ovirtmgmt bridge pre-created with 'bond0' as the only member, assigned a static IP address - firewall DISABLED - /etc/yum.repos.d/ovirt.rep has ONLY the 3.4.0 beta repo enabled: [ovirt-3.4.0-beta] name=3.4.0 beta testing repo for the oVirt project baseurl=http://ovirt.org/releases/3.4.0-beta/rpm/Fedora/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 - only other packages installed were "ntp" and "screen" - performed "yum install ovirt-hosted-engine-setup" then "screen" then "hosted-engine --deploy" Any guidance or things to test would be _greatly_ appreciated. Thanks! -Brad

5 14

[Users] hosted-engine setup fails on RHEL6
by Frank Wall 23 Jan '14

23 Jan '14

Hi, I'm currently trying to setup a hosted-engine on a RHEL6 host with nightly repository (because 3.4 BETA didn't work either): [root@host ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140123135916.log Version: otopi-1.2.0_master (otopi-1.2.0-0.2.master.20140121.git84f0852.el6) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination The full log is available here: http://pastebin.com/Xpa87sjc The matching log entry is below: 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:138 Stage customization METHOD otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._customization 2014-01-23 14:17:48 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND During customization use CTRL-D to abort. 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:630 _check_existing_pools 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 729, in _customization self._check_existing_pools() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request self.send_content(h, request_body) File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content connection.endheaders() File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders self._send_output() File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output self.send(msg) File "/usr/lib64/python2.6/httplib.py", line 739, in send self.connect() File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File "/usr/lib64/python2.6/socket.py", line 567, in create_connection raise error, msg error: [Errno 111] Connection refused 2014-01-23 14:17:48 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused RPM version information: otopi-1.2.0-0.2.master.20140121.git84f0852.el6.noarch ovirt-host-deploy-1.2.0-0.2.master.20140120.gitdeb0453.el6.noarch ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch ovirt-engine-sdk-python-3.4.0.2-1.20140121.git42b7d69.el6.noarch ovirt-release-el6-10.0.1-2.noarch vdsm-python-zombiereaper-4.14.1-6.gite008998.el6.noarch vdsm-python-4.14.1-6.gite008998.el6.x86_64 vdsm-cli-4.14.1-6.gite008998.el6.noarch vdsm-xmlrpc-4.14.1-6.gite008998.el6.noarch vdsm-4.14.1-6.gite008998.el6.x86_64 Any hint? Thanks - Frank

4 7

[Users] another networking question: ssh to VM with private dhcp addr
by Robert Story 23 Jan '14

23 Jan '14

--Sig_/w6my2qV.PKZtGA0U_nY_H5Y Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I've got oVirt 3.3.x all-in-one up and running on CentOS 6.3. The IP address on the ovirtmgmt bridge is static/public. I have not done any additional network/VLAN configuration. If I create a VM and give it an address on the same subnet, I can ssh to it just fine. If I create a VM and let it use dhcp, it gets a 172.31.x.x address. Outgoing access works fine, but I can't figure out what to do to allow me to be able to ssh into those VMs. With straight KVM the VM private network was on a virtual interface on the host, making it easy. But I can't figure out how to do it with oVirt. Any help greatly appreciated. Thanks in advance. Robert --Sig_/w6my2qV.PKZtGA0U_nY_H5Y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlLgpsIACgkQ7/fVLLY1mnj1fQCeMRXZlVEVu7TYhDOUMZptymdC upUAniuQzBrfuqKTazfNk3VjHPWozuPY =aRJj -----END PGP SIGNATURE----- --Sig_/w6my2qV.PKZtGA0U_nY_H5Y--

2 2

[Users] oVirt 3.4 release notes and what's new section empty
by Gianluca Cecchi 23 Jan '14

23 Jan '14

hello, at http://www.ovirt.org/OVirt_3.4.0_release_notes the what's new section seems to be empty. What major/minor features one would expect as added value passing from 3.3.3 to 3.4? Any other pointers? Thanks, Gianluca

2 1

[Users] disks successfully removed with torage failure message
by Gianluca Cecchi 23 Jan '14

23 Jan '14

Hello, 3.3.2 beta on Fedora 19 engine with 2 Fedora 19 hosts and GusterFS

4 10

[Users] Possible problems testing 3.3.3 RC
by Gianluca Cecchi 23 Jan '14

23 Jan '14

Hello, engine 3.3.3 beta1 on fedora 19 fully updated (for f19 repos). I would like to upgrade and test 3.3.3 RC I just updated ovirt-release so that now I have ovirt-release-fedora-10.0.1-2.noarch yum clean metadata modified new ovirt repofile enabling updates-testing and disabling beta [ovirt-stable] name=Older Stable builds of the oVirt project baseurl=http://ovirt.org/releases/stable/rpm/Fedora/$releasever/ [ovirt-3.3.2] name=oVirt 3.3.2 release baseurl=http://resources.ovirt.org/releases/3.3.2/rpm/Fedora/$releasever/ [ovirt-updates-testing] name=Test Updates builds of the oVirt project baseurl=http://ovirt.org/releases/updates-testing/rpm/Fedora/$releasever/ Even if ovirt update will be made through engine-setup, I presum that a "yum update" shouldn't give any depedency error, correct? Instead I have: # yum update Loaded plugins: langpacks, refresh-packagekit, versionlock Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-dwh.noarch 0:3.3.3-1.fc19 will be updated ---> Package ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be an update --> Processing Dependency: ovirt-engine-dwh-setup >= 3.4.0-0.2.master.20140122122024.fc19 for package: ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch ---> Package ovirt-engine-lib.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-lib.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-setup.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-setup.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-0.1.beta1.fc19 will be updated ---> Package ovirt-engine-websocket-proxy.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-image-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-image-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-iso-uploader.noarch 0:3.3.2-1.fc19 will be updated ---> Package ovirt-iso-uploader.noarch 0:3.3.3-1.fc19 will be an update ---> Package ovirt-log-collector.noarch 0:3.3.2-2.fc19 will be updated ---> Package ovirt-log-collector.noarch 0:3.3.3-1.fc19 will be an update --> Running transaction check ---> Package ovirt-engine-dwh-setup.noarch 0:3.4.0-0.2.master.20140122122024.fc19 will be installed --> Processing Dependency: ovirt-engine-setup-plugin-ovirt-engine-common for package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch --> Finished Dependency Resolution Error: Package: ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch (ovirt-updates-testing) Requires: ovirt-engine-setup-plugin-ovirt-engine-common You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Why ovirt-engine-dwh.noarch 0:3.4.0-0.2.master.20140122122024.fc19 is proposed as an update? Gianluca

3 5

[Users] Ovirt 3.3.2. and vdsm 4.14
by Federico Alberto Sayd 23 Jan '14

23 Jan '14

Hello: Why Ovirt 3.3.2. installs vdsm 4.14 on Centos 6.5?? I am installing 5 nodes with Centos 6.5. I have installed two nodes, I have added: 1 - epel repo (http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.r…) 2 - ovirt repo (http://ovirt.org/releases/ovirt-release-el.noarch.rpm) In the two first nodes Ovirt engine installed vdsm 4.13. Now I have installed the third node with the same repos and Ovirt installs vdsm 4.14 and when it tries to activate the node complains about the vdsm version, it says that vdsm version is not compatible: Host "my-third-node" is installed with VDSM version (4.14) and cannot join cluster Cluster-XXX which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. /etc/yum.repos.d in the trhee nodes are the same: CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo el6-ovirt.repo epel.repo epel-testing.repo glusterfs-epel.repo Why the difference? It is not suppossed that oVirt 3.3.2 should install vdsm 3.13 ?? Thanks, Federico

2 1