Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Simone Tiraboschi
On Fri, Oct 23, 2015 at 3:57 PM, Gianluca Cecchi wrote: > On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi > wrote: > >> >> >>> In case I want to setup a single host with self hosted engine, could I >>> configure on hypervisor >>> a) one NFS

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Gianluca Cecchi
On Fri, Oct 23, 2015 at 5:05 PM, Simone Tiraboschi wrote: > >> > OK, can you please try again the whole reboot procedure just to ensure > that it was just a temporary NFS glitch? > It seems reproducible. This time I was able to shutdown the hypervisor without manual power

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Simone Tiraboschi
On Fri, Oct 23, 2015 at 5:55 PM, Gianluca Cecchi wrote: > On Fri, Oct 23, 2015 at 5:05 PM, Simone Tiraboschi > wrote: > >> >>> >> OK, can you please try again the whole reboot procedure just to ensure >> that it was just a temporary NFS glitch? >>

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Gianluca Cecchi
On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi wrote: > > >> In case I want to setup a single host with self hosted engine, could I >> configure on hypervisor >> a) one NFS share for sh engine >> b) one NFS share for ISO DOMAIN >> c) a local filesystem to be used to

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Gianluca Cecchi
On Fri, Oct 23, 2015 at 6:10 PM, Simone Tiraboschi wrote: > > >> >> Probably inside the [unit] section I should add >> After=nfs-server.service >> >> > Ok, I understood. > You are right: the broker was failing cause the NFS storage was not ready > cause it was served in

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Simone Tiraboschi
On Fri, Oct 23, 2015 at 4:56 PM, Gianluca Cecchi wrote: > On Fri, Oct 23, 2015 at 4:42 PM, Simone Tiraboschi > wrote: > >> >> >> >> Are ovirt-ha-agent and ovirt-ha-broker up and running? >> Can you please try to restart them via systemd? >> >> >>

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-23 Thread Gianluca Cecchi
On Fri, Oct 23, 2015 at 4:42 PM, Simone Tiraboschi wrote: > > > > Are ovirt-ha-agent and ovirt-ha-broker up and running? > Can you please try to restart them via systemd? > > > In the mean time I found inside the logs they failed to start. I found in broker log the message

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Gianluca Cecchi
On Thu, Oct 22, 2015 at 3:01 PM, Simone Tiraboschi wrote: > >> >> Any particular file or section in log files to cross check? >> I can also start from scratch in case just to be sure that I don't >> get into same problem, so that it can be useful to find it before... >>

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Gianluca Cecchi
On Thu, Oct 22, 2015 at 5:08 PM, Simone Tiraboschi wrote: > >> engine is up and admin web portal accessible and host results up. >> >> I expected storage to be configured inside admin web portal but >> apparently I don't see anything already configured and also I don't see

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Gianluca Cecchi
On Thu, Oct 22, 2015 at 2:15 PM, Simone Tiraboschi wrote: > >> 2015-10-21 17:36:33 DEBUG otopi.plugins.otopi.dialog.machine >> dialog.__logString:219 DIALOG:SEND ### Please input VDSM certificate >> chain that matches certificate request, top is issuer >> 2015-10-21

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Simone Tiraboschi
On Thu, Oct 22, 2015 at 5:28 PM, Gianluca Cecchi wrote: > On Thu, Oct 22, 2015 at 5:08 PM, Simone Tiraboschi > wrote: > >> >>> engine is up and admin web portal accessible and host results up. >>> >>> I expected storage to be configured inside

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Simone Tiraboschi
On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi wrote: > > > On Thu, Oct 22, 2015 at 5:28 PM, Gianluca Cecchi < > gianluca.cec...@gmail.com> wrote: > >> On Thu, Oct 22, 2015 at 5:08 PM, Simone Tiraboschi >> wrote: >> >>> engine is up and admin

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Simone Tiraboschi
On Thu, Oct 22, 2015 at 4:28 PM, Gianluca Cecchi wrote: > On Thu, Oct 22, 2015 at 3:01 PM, Simone Tiraboschi > wrote: > >> >>> >>> Any particular file or section in log files to cross check? >>> I can also start from scratch in case just to be

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Simone Tiraboschi
On Thu, Oct 22, 2015 at 2:00 PM, Gianluca Cecchi wrote: > On Thu, Oct 22, 2015 at 11:50 AM, Gianluca Cecchi < > gianluca.cec...@gmail.com> wrote: > >> On Wed, Oct 21, 2015 at 6:15 PM, Simone Tiraboschi >> wrote: >> >>> >>> It pools engine REST API

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Gianluca Cecchi
On Wed, Oct 21, 2015 at 6:15 PM, Simone Tiraboschi wrote: > > It pools engine REST API checking the host status for 10 minutes till it > become 'up' or 'non_operational'. In your case it reached the 10 minutes > timeout. > Please check engine and host-deploy logs on the

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Simone Tiraboschi
On Thu, Oct 22, 2015 at 2:29 PM, Gianluca Cecchi wrote: > On Thu, Oct 22, 2015 at 2:15 PM, Simone Tiraboschi > wrote: > >> >>> 2015-10-21 17:36:33 DEBUG otopi.plugins.otopi.dialog.machine >>> dialog.__logString:219 DIALOG:SEND ### Please

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-22 Thread Gianluca Cecchi
On Thu, Oct 22, 2015 at 11:50 AM, Gianluca Cecchi wrote: > On Wed, Oct 21, 2015 at 6:15 PM, Simone Tiraboschi > wrote: > >> >> It pools engine REST API checking the host status for 10 minutes till it >> become 'up' or 'non_operational'. In your

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-21 Thread Simone Tiraboschi
On Wed, Oct 21, 2015 at 4:43 PM, Gianluca Cecchi wrote: > On Wed, Oct 21, 2015 at 4:08 PM, Yedidyah Bar David > wrote: > >> On Wed, Oct 21, 2015 at 5:00 PM, Gianluca Cecchi >> wrote: >> > Hello, >> > playing with an

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-21 Thread Yedidyah Bar David
On Wed, Oct 21, 2015 at 5:00 PM, Gianluca Cecchi wrote: > Hello, > playing with an environment where I have a CentOS 7.1 + updates server with > 3.6 repos configured. > no DNS resolution in place. > running the command > hosted-engine --deploy > > I initially get,

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-21 Thread Gianluca Cecchi
On Wed, Oct 21, 2015 at 4:08 PM, Yedidyah Bar David wrote: > On Wed, Oct 21, 2015 at 5:00 PM, Gianluca Cecchi > wrote: > > Hello, > > playing with an environment where I have a CentOS 7.1 + updates server > with > > 3.6 repos configured. > > no DNS

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-21 Thread Gianluca Cecchi
On Wed, Oct 21, 2015 at 4:58 PM, Simone Tiraboschi wrote: > >> Ok, I will crosscheck the output... >> > > That question is: > Add lines for the appliance itself and for this host to /etc/hosts on the > engine VM? > Note: ensuring that this host could resolve the engine VM

Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error

2015-10-21 Thread Simone Tiraboschi
On Wed, Oct 21, 2015 at 5:44 PM, Gianluca Cecchi wrote: > On Wed, Oct 21, 2015 at 4:58 PM, Simone Tiraboschi > wrote: > >> >>> Ok, I will crosscheck the output... >>> >> >> That question is: >> Add lines for the appliance itself and for this host