[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-26 Thread Martin Sivak
[root @ h4 /] # sanlock direct init -s hosted-engine: 0: > /rhev/data-center/mnt/ssd.lan \: _ ovirt / > 8905c9ac-d892-478d-8346-63b8fa1c5763 / images / badd5883-ef71- > 45bb-9073-a573f46a3b44 / e4408917-fe00-4567-8db0-bf464472ec01.lockspace > init done -19 Do you really have all those spaces in

[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-25 Thread Reznikov Alexei
25.06.2018 15:12, Martin Sivak пишет: Hi, yes there is a solution described directly in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1521011#c20 The provided script worked only for cases that had the necessary disks, but where the uuids were not written to the config files. You need

[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-25 Thread Martin Sivak
Hi, yes there is a solution described directly in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1521011#c20 The provided script worked only for cases that had the necessary disks, but where the uuids were not written to the config files. You need to follow the procedure from comment 20

[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-25 Thread Reznikov Alexei
25.06.2018 13:05, Simone Tiraboschi пишет: On Mon, Jun 25, 2018 at 10:19 AM Reznikov Alexei mailto:reznikov...@soskol.com>> wrote: 21.06.2018 20:15, reznikov...@soskol.com пишет: > Hi list! > > After upgrade my cluster from 4.1.9 to 4.2.2,

[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-25 Thread Simone Tiraboschi
On Mon, Jun 25, 2018 at 10:19 AM Reznikov Alexei wrote: > 21.06.2018 20:15, reznikov...@soskol.com пишет: > > Hi list! > > > > After upgrade my cluster from 4.1.9 to 4.2.2, agent and broker can't > > start on host... > > > > cat /var/log/ovirt-hosted-engine-ha/agent.log > >

[ovirt-users] Re: Broker fails to start after upgrade 4.1 to 4.2 metadata_image_UUID can't be ''

2018-06-25 Thread Reznikov Alexei
21.06.2018 20:15, reznikov...@soskol.com пишет: Hi list! After upgrade my cluster from 4.1.9 to 4.2.2, agent and broker can't start on host... cat /var/log/ovirt-hosted-engine-ha/agent.log MainThread::ERROR::2018-06-21