rajujith commented on issue #5803: URL: https://github.com/apache/cloudstack/issues/5803#issuecomment-1604008959
@edikevich I believe what you are observing is expected behavior as per the current design. I believe this is your use scenario: Zone with multiple pods At least one pod is shared but it is running VMs( all hosts) belonging to other domain/s. Compute offering uses strict Implicit Dedication. DeployVirtualMachine API call doesn't have an affinity group In this scenario, the dedicated pod won't be selected for deployment since the related affinity group is selected subsequently the 'strict Implicit Dedication' avoid the shared pod since it has VMs belonging to other domain/s resulting in no remaining host to deploy in the given zone. To the best of my knowledge, this VM deployment error in this scenario is expected. You could use the affinity group for VM deployment to avoid this failure. CC @DaanHoogland Note: My verifications are based on CS v 4.18. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
