Il 12/02/2015 14:16, Yedidyah Bar David ha scritto:
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Yeela Kaplan" <ykaplan@redhat.com>, "Alon Bar-Lev" <alonbl@redhat.com>, "Allon Mureinik" <amureini@redhat.com>, "Yaniv Dary" <ydary@redhat.com>, "Federico Simoncelli" <fsimonce@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "Yedidyah Bar David" <didi@redhat.com>, "Simone Tiraboschi" <stirabos@redhat.com>, devel@ovirt.org, "Michal Skrivanek" <mskrivan@redhat.com> Sent: Thursday, February 12, 2015 2:55:57 PM Subject: [HC] Weird issue while deploying hosted-engine
While deploying Hosted Engine on Hyper Converged Gluster Storage I've hit the following issue.
ovirt-hosted-engine-setup:
[ INFO ] Engine replied: DB Up!Welcome to Health Status! Enter the name of the cluster to which you want to add the host (Default) [Default]: [ INFO ] Waiting for the host to become operational in the engine. This may take several minutes... [ INFO ] Still waiting for VDSM host to become operational...
Accessed to the engine, VM and engine working correctly, installed using 3.5 snapshot repositories. host-deploy started on the host (see attached logs) and got stuck at:
2015-02-12 13:08:33 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND ### Response is VALUE TIME=type:value or ABORT TIME
Not sure about the rest, but this seems to be some time checking issue. Did not check the sources, only my own host-deploy logs. My guess:
otopi (internal plugin?) checks the system clock. It tries ntpq, which failed for you, then chronyc - on my system, you do not seem to have it - and then just asks the engine for the time, and perhaps the engine does not know how to reply. Try installing chrony.
Not sure that chrony is really needed, I've ntpd. But I've seen that by default it's not enabled on RHEL 7.1. # service ntpd status Redirecting to /bin/systemctl status ntpd.service ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled) Active: inactive (dead) and host-deploy doesn't check if it's alive before calling /sbin/ntpq -c rv I'm not sure about what the engine should send in this case because the VM get paused here. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com