Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-21 Thread Jamie Lawrence
> On Apr 21, 2017, at 6:38 AM, knarra wrote: > > On 04/21/2017 06:34 PM, Jamie Lawrence wrote: >>> On Apr 20, 2017, at 10:36 PM, knarra wrote: The installer claimed it did, but I believe it didn’t. Below the error from my original email, there’s

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-21 Thread knarra
On 04/21/2017 06:34 PM, Jamie Lawrence wrote: On Apr 20, 2017, at 10:36 PM, knarra wrote: The installer claimed it did, but I believe it didn’t. Below the error from my original email, there’s the below (apologies for not including it earlier; I missed it). Note:

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-21 Thread Jamie Lawrence
> On Apr 20, 2017, at 10:36 PM, knarra wrote: >> The installer claimed it did, but I believe it didn’t. Below the error from >> my original email, there’s the below (apologies for not including it >> earlier; I missed it). Note: 04ff4cf1-135a-4918-9a1f-8023322f89a3 is the

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-20 Thread knarra
On 04/20/2017 10:48 PM, Jamie Lawrence wrote: On Apr 19, 2017, at 11:35 PM, knarra wrote: On 04/20/2017 03:15 AM, Jamie Lawrence wrote: I trialed installing the hosted engine, following the instructions at

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker (revised)

2017-04-20 Thread Jamie Lawrence
> On Apr 20, 2017, at 9:18 AM, Simone Tiraboschi wrote: > Could you please share the output of > sudo -u vdsm sudo service sanlock status That command line prompts for vdsm’s password, which it doesn’t have. But output returned as root is below. Is that ‘operation not

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-20 Thread Jamie Lawrence
> On Apr 19, 2017, at 11:35 PM, knarra wrote: > > On 04/20/2017 03:15 AM, Jamie Lawrence wrote: >> I trialed installing the hosted engine, following the instructions at >> http://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/ >> . This is using

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker (revised)

2017-04-20 Thread Simone Tiraboschi
On Thu, Apr 20, 2017 at 2:14 AM, Jamie Lawrence wrote: > > So, tracing this further, I’m pretty sure this is something about sanlock. > > As best I can tell this[1] seems to be the failure that is blocking > importing the pool, creating storage domains, importing the

Re: [ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-20 Thread knarra
On 04/20/2017 03:15 AM, Jamie Lawrence wrote: I trialed installing the hosted engine, following the instructions at http://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/ . This is using Gluster as the backend storage subsystem. Answer file at the end. Per the

[ovirt-users] Hosted engine install failed; vdsm upset about broker (revised)

2017-04-19 Thread Jamie Lawrence
So, tracing this further, I’m pretty sure this is something about sanlock. As best I can tell this[1] seems to be the failure that is blocking importing the pool, creating storage domains, importing the HE, etc. Contrary to the log, sanlock is running; I verified it starts on system-boot and

[ovirt-users] Hosted engine install failed; vdsm upset about broker

2017-04-19 Thread Jamie Lawrence
I trialed installing the hosted engine, following the instructions at http://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/ . This is using Gluster as the backend storage subsystem. Answer file at the end. Per the docs, "When the hosted-engine deployment script