[ovirt-users] Hosts force fencing after engine upgrade 4.3->4.4

Hi, I was in the process of upgrading 4.3 to 4.4. First I upgraded the engine and the hosts are still 4.3. The engine has started fencing my hosts as there has been 1 (one) connection problem to VDSM on the host. I Basically, the engine at some random time connects to vdsm, this crashes (didnt on e4.3) and after a few seconds the engine issues a fencing and all my VMs are taken down .... This happend with multiple hosts at random times. Can this be attributed to the unmatched hosts? Or should I consider an engine restore to 4.3? Engine ovirt-engine-4.4.10.7-1.el8.noarch: 2022-11-21 10:40:05,788+01 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-16) [258de39e] Command 'UploadStreamVDSCommand(HostName = galador, UploadStreamVDSCommandParameters:{hostId='146456e8-02fd-4 ce0-9140-13032d9a52ca'})' execution failed: java.net.SocketException: Connection reset by peer (Write failed) HOST vdsm-4.30.46-1.el7.x86_64: 2022-11-21 10:40:05,785+0100 ERROR (Reactor thread) [vds.dispatcher] uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:10.10.80.100', 37772, 0, 0) at 0x7f73cba72710> (<type 'exceptions.TypeError'>:object of type 'NoneType' has no len() [/usr>