Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Tue, Jun 28, 2016 at 06:06:39PM +0200, Simone Tiraboschi wrote: > On Tue, Jun 28, 2016 at 5:24 PM, Dan Kenigsberg wrote: > > On Tue, Jun 28, 2016 at 04:08:51PM +0200, Simone Tiraboschi wrote: > >> On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: >

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

HI to All!! Il 28/06/2016 17.24, Stefano Danzi ha scritto: [CUT] We have two issues here. First is that https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 is still using

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Tue, Jun 28, 2016 at 5:24 PM, Dan Kenigsberg wrote: > On Tue, Jun 28, 2016 at 04:08:51PM +0200, Simone Tiraboschi wrote: >> On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: >> > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: >> >>

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Tue, Jun 28, 2016 at 04:08:51PM +0200, Simone Tiraboschi wrote: > On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: > > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: > >> Hi! > > > > > > Thanks for the detailed logging! > > > >> > >> The broker error

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

Il 28/06/2016 15.02, Dan Kenigsberg ha scritto: On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: Hi! Thanks for the detailed logging! The broker error is: ==> /var/log/ovirt-hosted-engine-ha/agent.log <== MainThread::INFO::2016-06-27

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: >> Hi! > > > Thanks for the detailed logging! > >> >> The broker error is: >> >> ==> /var/log/ovirt-hosted-engine-ha/agent.log <== >>

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: > Hi! Thanks for the detailed logging! > > The broker error is: > > ==> /var/log/ovirt-hosted-engine-ha/agent.log <== > MainThread::INFO::2016-06-27 >

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

Hi! The broker error is: ==> /var/log/ovirt-hosted-engine-ha/agent.log <== MainThread::INFO::2016-06-27 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id 140293563619152 ==> /var/log/ovirt-hosted-engine-ha/broker.log <==

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Fri, Jun 24, 2016 at 06:45:24PM +0200, Stefano Danzi wrote: > HI!! > > I found a workaround > > the brocker process try to connect to vdsm to IPV4 host address using an > IPV6 connection > (I noticed that doing a strace to the process), > but ipv6 is not intialized at

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

HI!! I found a workaround the brocker process try to connect to vdsm to IPV4 host address using an IPV6 connection (I noticed that doing a strace to the process), but ipv6 is not intialized at boot. (why connect to IPV4 address using IPV6?) I added the following lines

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

How I can change self hosted engine configuration to mount directly gluster storage without pass through gluster NFS? Maybe this solve Il 24/06/2016 10.16, Stefano Danzi ha scritto: After an additional yum clean all && yum update was updated some other rpms. Something changed. My

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

After an additional yum clean all && yum update was updated some other rpms. Something changed. My setup has engine storage on gluster, but mounted with NFS. Now gluster daemon don't automatically start at boot. After starting manually gluster the error is the same: ==>

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

Hi! After cleanin metadata yum do an update of vdsm: [root@ovirt01 ~]# rpm -qva | grep vdsm vdsm-yajsonrpc-4.18.4.1-0.el7.centos.noarch vdsm-infra-4.18.4.1-0.el7.centos.noarch vdsm-cli-4.18.4.1-0.el7.centos.noarch vdsm-python-4.18.4.1-0.el7.centos.noarch

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

On Thu, Jun 23, 2016 at 6:36 PM, Stefano Danzi wrote: > > Hi! > I've just upgrade oVirt from 3.6 to 4.0 and I'm not able to start the self > hosted engine. > Hi Stefano, can you please try "yum clean metadata" "yum update" again? You should get vdsm 4.18.4.1, please let us

Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

> On 23 Jun 2016, at 18:36, Stefano Danzi wrote: > > > Hi! > I've just upgrade oVirt from 3.6 to 4.0 and I'm not able to start the self > hosted engine. > > first thing is that the host network lose the degaut gateway configuration. > But this is not the problem. > >

[ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

Hi! I've just upgrade oVirt from 3.6 to 4.0 and I'm not able to start the self hosted engine. first thing is that the host network lose the degaut gateway configuration. But this is not the problem. Logs: ==> /var/log/ovirt-hosted-engine-ha/agent.log <== MainThread::INFO::2016-06-23