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

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 when no disks for lockspace and metadata exist at all. Best regards Martin Sivak On Mon, Jun 25, 2018 at 9:52 AM, Reznikov Alexei <reznikov_aa(a)soskol.com&gt; wrote: > 21.06.2018 20:15, reznikov_aa(a)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 >> 03:25:34,603::hosted_engine::538::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) >> Failed to start necessary monitors >> MainThread::ERROR::2018-06-21 >> 03:25:34,604::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) >> Traceback (most recent call last) >> >> cat /var/log/ovirt-hosted-engine-ha/broker.log >> MainThread::INFO::2018-06-21 >> 03:25:40,406::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) >> Finished loading submonitors >> MainThread::WARNING::2018-06-21 >> 03:25:40,406::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) >> Can't connect vdsm storage: 'metadata_image_UUID can't be '' >> >> cat /etc/ovirt-hosted-engine/hosted-engine.conf | grep metadata_image >> metadata_image_UUID= >> >> Also is: >> cat /etc/ovirt-hosted-engine/hosted-engine.conf | grep lock >> lockspace_image_UUID= >> lockspace_volume_UUID= >> >> This bug is very much like this >> https://bugzilla.redhat.com/show_bug.cgi?id=1521011 My cluster started with >> version 3.3... >> >> But i can't resolution this bug correctly. >> >> Guru please help me!!! >> >> Thanx, Alex! >>