Hello camealy,
Welcome (back) to Communities.
Are they becoming 'Not responding' state? If hosts are becoming non-responsive to vCenter then cluster-level tasks such as On-disk format (or anything else that requires communication between multiple hosts and vCenter e.g. vMotion) will timeout or fail - not being able to upgrade ODF is just a side-effect and the root cause should be identified and resolved as a priority, typical causes are poor or misconfigured management networks or issues with vCenter.
If the hostd aspect is fine (e.g. hosts are NOT entering a 'Not responding' state periodically), then the other probable problematic component is vsanmgmtd which runs on each host and is responsible for a lot of the vSAN-vCenter operations (e.g. vSAN Health, Disk Management and vSAN performance stats) - the most common issues with this service are not with the service itself but that it can be negatively impacted by 3rd-party applications (particularly monitoring applications such as Veeam ONE) which (depending on a number of factors) can overburden this daemon and/or other services that it depends on - a typical symptom of this is observing the daemon frequently running out of system-memory which may be indicated by 'MEMORY PRESSURE' messages being logged in vsanmgmtd.log.
As this is a potentially broad topic (e.g. it is not just a case of one possible root cause issue) and that it can be symptomatic of other misconfigurations/issues in the environmentm, I would advise opening a Support Request with my colleagues in GSS vSAN if you have a valid support account that can be used.
Bob
