Pool provisioning operations are not initiated after doing view upgrade for VMware Horizon 7 version 7.5.x due to the stale jars left behind after upgrade. We see the error messages Pool Info currently inconsistent, skipping determineActions for pool in CS logs at C:\ProgramData\VMware\VDM\logs. Execute below steps on the brokers one at a time and repeat the steps for the other brokers in the cluster.
Resolution
Step 1: Uninstall broker and adam db.
Step 2: Ensure that all the view folders and jars are deleted.
Step 3: Perform fresh installation of the broker as replica pointing to another standard server.
Reference
VMware Knowledge Base: Pool provisioning fails after upgrade (59808)
Alex Lim
Alex Lim is a certified IT Technical Support Architect with over 15 years of experience in designing, implementing, and troubleshooting complex IT systems and networks. He has worked for leading IT companies, such as Microsoft, IBM, and Cisco, providing technical support and solutions to clients across various industries and sectors. Alex has a bachelor’s degree in computer science from the National University of Singapore and a master’s degree in information security from the Massachusetts Institute of Technology. He is also the author of several best-selling books on IT technical support, such as The IT Technical Support Handbook and Troubleshooting IT Systems and Networks. Alex lives in Bandar, Johore, Malaysia with his wife and two chilrdren. You can reach him at [email protected] or follow him on Website | Twitter | Facebook
