Not ready yet,
> ignoring event u'|virt|VM_status|0b7d02df-0286-4e0e-a50b-1d02915ba81c'
> args={u'0b7d02df-0286-4e0e-a50b-1d02915ba81c': {'status': 'Up', 'username':
> 'Unknown', 'memUsage': '36', 'guest
tled WARN MOM not
available.
Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm throttled WARN MOM not
available, KSM stats will be missing.
Nov 14 21:01:34 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
ignoring event u'|virt|VM_status|0b7d02df-0286-4e0e-a50b-1d02915ba81c'
args=
Try restarting vdsmd from the shell, “systemctl restart vdsmd”.
> From: Artem Tambovskiy
> Subject: [ovirt-users] Non-responsive host, VM's are still running - how to
> resolve?
> Date: November 14, 2017 at 11:23:32 AM CST
> To: users
>
> Apparently, i lost the hos
Apparently, i lost the host which was running hosted-engine and another 4
VM's exactly during migration of second host from bare-metal to second host
in the cluster. For some reason first host entered the "Non reponsive"
state. The interesting thing is that hosted-engine and all other VM's up
and r
4 matches
Mail list logo