Why hosts went to not responding status and VMs to unknown after OVF update fails with error java.net.SocketTimeoutException

Solution In Progress - Updated -

Issue

  • The OVF store update fails with the below error in the engine log:
2022-03-30 01:42:47,265Z ERROR [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-41) [6093d872] Command 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: java.net.SocketTimeoutException: Read timed out (Failed with error VDS_NETWORK_ERROR and code 5022)
  • Subsequently, the host was moved into "not responding" status, and VMs were moved to unknown and then host was fenced.

Environment

  • Red Hat Virtualization 4.4.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content