[ovirt-devel] VDSM network error during all-in-one setup of oVirt 3.5 beta2 on fedora20

[Simone Tiraboschi]

Hi,
I'm trying to install oVirt 3.5 beta 2 in all-in-one mode on fedora20 but I'm getting an error from VDSM with doesn't seam to start when required probably due to an error during network configuration.

engine-setup simply gives me:
[ INFO  ] Still waiting for VDSM host to become operational...
[ ERROR ] The VDSM host was found in a failed state. Please check engine and bootstrap installation logs.
[WARNING] Local storage domain not added because the VDSM host was not up. Please add it manually.


in /var/log/vdsm/vdsm.log I'm finding:

MainThread::INFO::2014-07-08 10:44:55,720::vdsm::141::vds::(run) <Thread(Thread-14, started 139845947094784)>
MainThread::INFO::2014-07-08 10:44:55,720::vdsm::141::vds::(run) <WorkerThread(Thread-10, started daemon 139846668506880)>
MainThread::INFO::2014-07-08 10:44:55,720::vdsm::141::vds::(run) <WorkerThread(Thread-1, started daemon 139847214704384)>
MainThread::INFO::2014-07-08 10:44:55,720::vdsm::141::vds::(run) <WorkerThread(Thread-9, started daemon 139846676899584)>
MainThread::INFO::2014-07-08 10:44:55,721::vdsm::141::vds::(run) <GuestManager(GuestManager, started daemon 139846062266112)>
MainThread::INFO::2014-07-08 10:44:55,721::vdsm::141::vds::(run) <WorkerThread(Thread-6, started daemon 139847172740864)>
VM Channels Listener::INFO::2014-07-08 10:44:56,218::vmchannels::183::vds::(run) VM channels listener thread has ended.
Thread-14::ERROR::2014-07-08 10:44:56,884::BindingXMLRPC::1126::vds::(wrapper) unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/rpc/BindingXMLRPC.py", line 1110, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/rpc/BindingXMLRPC.py", line 535, in setupNetworks
    return api.setupNetworks(networks, bondings, options)
  File "/usr/share/vdsm/API.py", line 1334, in setupNetworks
    supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>
    **kwargs)
  File "<string>", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in _callmethod
    kind, result = conn.recv()
EOFError


Did someone else notice similar problems with latest VDSM?

On my system I have:
vdsm.x86_64                     4.16.0-42.git3bfad86.fc20
vdsm-cli.noarch                 4.16.0-42.git3bfad86.fc20
vdsm-jsonrpc.noarch             4.16.0-42.git3bfad86.fc20
vdsm-jsonrpc-java.noarch        1.0.0-0.0.master.fc20
vdsm-python.x86_64              4.16.0-42.git3bfad86.fc20
vdsm-python-zombiereaper.noarch 4.16.0-42.git3bfad86.fc20
vdsm-xmlrpc.noarch              4.16.0-42.git3bfad86.fc20
vdsm-yajsonrpc.noarch           4.16.0-42.git3bfad86.fc20

thanks,
Simone