[Users] Fedora 19 Host Installation Failed - VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]

Moti Asayag masayag at redhat.com
Wed Feb 26 10:25:36 UTC 2014



----- Original Message -----
> From: "Alon Bar-Lev" <alonbl at redhat.com>
> To: "Udaya Kiran P" <ukiran770 at yahoo.in>, "Moti Asayag" <masayag at redhat.com>
> Cc: fabiand at redhat.com, "users" <users at ovirt.org>
> Sent: Wednesday, February 26, 2014 12:08:43 PM
> Subject: Re: Fedora 19 Host Installation Failed - VDSM version (<UNKNOWN>) and cannot join cluster Default which is
> compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]
> 
> 
> 
> ----- Original Message -----
> > From: "Udaya Kiran P" <ukiran770 at yahoo.in>
> > To: alonbl at redhat.com, fabiand at redhat.com, "users" <users at ovirt.org>
> > Sent: Wednesday, February 26, 2014 12:02:24 PM
> > Subject: Fedora 19 Host Installation Failed - VDSM version (<UNKNOWN>) and
> > cannot join cluster Default which is
> > compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]
> > 
> > Hi Alon/Fabian,
> > 
> > I am trying to add the Fedora 19 host to oVirt Engine 3.3.2-1.fc19.
> 
> Why don't you use 3.3.3? issues may have been solved.
> 
> > 
> > Host installation failed with the below logs in the Events. I have attached
> > the Engine, Server and HostDeploy logs.
> 

The first error i see within the host-deploy log (line 4427) is:

2014-02-26 01:21:15 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages plugin.executeRaw:383 execute-result: ('/bin/vdsm-tool', 'configure', '--force'), rc=1
2014-02-26 01:21:15 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages plugin.execute:441 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stdout:
Usage: /bin/vdsm-tool [options] <action> [arguments]

Valid options:
  -h, --help
...
2014-02-26 01:21:15 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages packages._reconfigure:154 Cannot reconfigure vdsm using vdsm-tool

Alon, it looks like incorrect parameters were provided to vdsm-tool.

However, it looks that vdsmd service was restarted afterwards (line 4627):
2014-02-26 01:21:22 DEBUG otopi.plugins.otopi.services.systemd systemd.state:134 starting service vdsmd
2014-02-26 01:21:22 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:366 execute: ('/bin/systemctl', 'start', 'vdsmd.service'), executable='None', cwd='None', env=None
2014-02-26 01:21:30 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:383 execute-result: ('/bin/systemctl', 'start', 'vdsmd.service'), rc=0

At this point host deploy is finished and now the network is being configured on the
host. In order to do so - the engine 'pings' vdsm, until it is becomes responsive - which is not in this case.

All the tale is just for asking to provide /var/log/vdsm/vdsm.log, /var/log/vdsm/supervdsm.log and /var/log/messages from the host so we could examine why vdsm failed to start.

Were you able to run locally 'vdsClient -s localhost getVdsCaps' ?



> Moti?
> 
> 2014-02-26 01:21:32,622 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:32,636 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] Command PollVDS execution failed. Exception: RuntimeException:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:33,167 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:33,169 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] Command PollVDS execution failed. Exception: RuntimeException:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:33,682 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:33,684 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] Command PollVDS execution failed. Exception: RuntimeException:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:34,191 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:34,192 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] Command PollVDS execution failed. Exception: RuntimeException:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2014-02-26 01:21:35,372 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] org.ovirt.engine.core.vdsbroker.vdsbroker.VDSRecoveringException:
> Failed to initialize storage
> 2014-02-26 01:21:35,373 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] Command PollVDS execution failed. Exception:
> VDSRecoveringException: Failed to initialize storage
> 2014-02-26 01:21:36,006 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-7)
> [7e2148] org.ovirt.engine.core.vdsbroker.vdsbroker.VDSRecoveringException:
> Failed to initialize storage
> 
> 
> 
> > 
> > Please suggest.
> > 
> > Thank You.
> > 
> > Events Log in oVirt Portal
> > =====================
> > 
> > 2014-Feb-26, 12:00
> > Host FC19HostBay16 is installed with VDSM version (<UNKNOWN>) and cannot
> > join
> > cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11,
> > 4.12, 4.10].
> > 
> > 2014-Feb-26, 11:55
> > Host FC19HostBay16 was autorecovered.
> > 
> > 2014-Feb-26, 11:55
> > Host FC19HostBay16 is installed with VDSM version (<UNKNOWN>) and cannot
> > join
> > cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11,
> > 4.12, 4.10].
> > 
> > 2014-Feb-26, 11:54
> > Host FC19HostBay16 failed to recover.
> > 
> > 2014-Feb-26, 11:51
> > Host FC19HostBay16 is initializing. Message: Failed to initialize storage
> > 
> > 2014-Feb-26, 11:51
> > Host FC19HostBay16 installation failed. Network error during communication
> > with the host.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stage: Termination.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Retrieving installation logs to:
> > '/var/log/ovirt-engine/host-deploy/ovirt-20140226012131-10.10.22.114-7e2148.log'.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stage: Pre-termination.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Starting vdsm.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stopping libvirtd.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stage: Closing up.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stage: Transaction commit.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Enrolling certificate.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Setting time.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Stage: Misc configuration.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Yum Verify: 134/134:
> > perl-HTTP-Negotiate.noarch 0:6.01-5.fc19 - u.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Yum Verify: 133/134: perl-HTML-Parser.x86_64
> > 0:3.71-1.fc19 - u.
> > 
> > 2014-Feb-26, 11:51
> > Installing Host FC19HostBay16. Yum Verify: 132/134: python-netaddr.noarch
> > 0:0.7.5-6.fc19 - u.
> > 
> > 
> > 
> > Regards,
> > Udaya Kiran
> 



More information about the Users mailing list