justinestruch commented on issue #11081: URL: https://github.com/apache/cloudstack/issues/11081#issuecomment-3140485340
Hi @DaanHoogland This is now working. For some reason cloudstack was still trying to use the old VM template in Vmware, although the system image in cloudstack was referring to the new 4.20.2 image from the secondary storage. I then renamed the old system VM template inside of Vsphere, then cloudstack picked up on this change and deployed the new 4.20.2 OVA and created the new vm template. Then I ran into another issue. When cloudstack was trying to deploy the new system template it could not find a suitable primary storage for the VMs. I was getting the error "StoragePool is in avoid set, skipping this pool to allocation of disk" in the management.log for the VSAN. I found a previous thread https://lists.apache.org/thread/1km9ntpr7s8z8ntx9jwllqq8bogdm23p that had a similar issue. The fix for me was the same, to delete the entry from the DB of the old template. Then after some time, cloudstack recreated the DB entry and the system VMs deployed and the Agent status came up automatically. I do notice these system VMs show as version 4.20.1.0 in cloudstack. I'm not sure if this is any concern but they are working fine. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
