Re: [ovirt-users] 3.5 to 3.6 upgrade stuck
On Thu, Jul 21, 2016 at 7:14 AM, Robert Story <rstory(a)tislabs.com> wrote:
I have a 3.5 hosted-engine with 5 el7 nodes. Today I tried upgrading
to 3.6.
The engine upgrade went great, no problems.
I had a host in maintenance mode, so I added the 3.6 repos and ran yum
update. I waited for the upgrade successful message. I checked the score
for the node, and it was still 2400, not 3400. Tried rebooting, but no
luck. So I put another host in maintenance mode, and had the same result.
MainThread::INFO::2016-07-20
23:44:30,352::upgrade::1031::ovirt_hosted_engine_ha.lib.upgrade.StorageServer::(upgrade_35_36)
Successfully upgraded
Everything seams OK on the upgrade path.
Both nodes are getting this error:
MainThread::ERROR::2016-07-21
01:05:04,187::brokerlink::279::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(_communicate)
Connection closed: Connection timed out
MainThread::ERROR::2016-07-21
01:05:04,188::agent::205::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Error:
'Failed to start monitor <type 'type'>, options {'hostname':
'poseidon.netsec'}: Connection timed out' - trying to restart agent
Can you please attach also broker.log? maybe the issue is somewhere else.
I've attached logs from the second host coming up after a reboot,
along
with engine log from the same timeframe.
Any suggestions on a way forward would be greatly appreciated.
Robert
--
Senior Software Engineer @ Parsons
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users