Comment 2 for bug 1957060

I would focus on the apparent network issue. The repeating error noted in the description ("Process execution error in _get_host_uuid: Unexpected error while running command.") is a red herring caused by nova's get_volume_connector() [1] calling os-brick's get_connector_properties() function.

[1] https://opendev.org/openstack/nova/src/branch/master/nova/virt/libvirt/driver.py#L1682
[2] https://opendev.org/openstack/os-brick/src/branch/master/os_brick/initiator/connector.py#L196

The os-brick code loops over every connection protocol, some of which are likely not available in the underlying hardware. In this case, the log message is due to the nvmeof protocol not being supported. There's a similar message just before it that states, "No Fibre Channel support detected on system."