Yeah, I saw that in the notes, that's why I gave it a long, long time to update... but those log entries seemed to indicate something was broken, the way they repeated almost the entire time after I initiated the update. I did find that my VEEAM instance kicked on for some jobs, and though maybe that was causing the issue (as it uses vcenter to stage / manage the VMs during backups), so I shut it down, rolled back to 5.1 (snapshots are awesome), and am now trying again.
↧