It just hasn’t fully flooded /tmp just yet. However I feel maybe there’s a bit of the known HPE bug as mentioned the last time this happened. Huh, Now note this host was installed running the official VMware Image provided by HPE for this exact hardware supported by the VMware HCL. OK I guess… moving on… the very next error event was: Could not stage image profile '(Updated) HPE-ESXi-Image': ('VMware_bootbank_vmware-fdm_7.0.2-18455184', ' No space left on device') This seemed a bit weird but I could find any info other than what’s usuallly a very Microsoft type answer of “you can just ignore it” or “ usually this is not an issue, just it says vCenter saying it is connecting to esxi host and installing it’s agent”
VMWARE ESXI 6 NFS4CLIENT LOADED SUCCESSFULLY STUCK INSTALL
Which was in the log right after this event of attempting to install a base ESXi image? Installing image profile '(Updated) HPE-ESXi-Image' with acceptance level checking disabled As a result, the file /tmp/img-stg/data/vmware_f.v00 could not be written Which showed only 90% full, which was still pretty high, which might have explained the one log event that I did see about it: The ramdisk 'tmp' is full. Un like the last time this happened, the event log wasn’t as blatant (flooded) complaining about the /tmp being full. This time after updating again a host in the cluster had the error message. This seems to be a reoccurring story these last couple posts… Error on Host Another vCenter Patch, Another problem ?