On Fri, Aug 10, 2018 at 10:08 PM, <g.vasilopoulos@uoc.gr> wrote:

today our network administration did some upgrades on the networking equipment, so the engine vlan went down for a while. Afterwards when it came back up 3 hosts was found as non responding, I couldn't see anything suspicious on the hosts, the problem "fixed" itself when I restarted the ovirt-engine service on the engine vm. Another "strange" side effect is that gluster was in need of healing constantly afterwards it did heal and desynch again almost immediately, whitch was "fixed" by shutting down and starting the vm's who were up at the time of the network outage.. I've seen this behaviour once more regarding the engine service, is this normal behaviour (e.g. to make the admin check if everything is ok) or is there something wrong ?

This is not normal. The engine.log from the time you experienced problem would help identify issue. _______________________________________________

Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org 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/users@ovirt.org/ message/SHYGOTIKL6GXGXLBIVDQB44NGXXEHX3F/