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!
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/GW2F456G5UHRZ4BNQQUN3XBSIM5COT7O/
