AnsweredAssumed Answered

Why is there a vMotion automation stop after updating? (Release 5.2 - 5.5)

Question asked by aaron.bolthouse on Jul 9, 2015
Latest reply on Dec 13, 2016 by swagner

I was wondering if anyone else has seen this behavior on their deployments. Since I updated to 5.2 and all builds since, the appliance will automate as configured for 4-5 days then it will stop and require manual interactions to perform moves. If I reboot the appliance it starts automating again. Any thoughts on how to remedy this?