Hi Devs, $subject.
This is happening because after initial information model is built (IaasProvider object), it does not get re-built to detect any changes. The mail thread [1] also describes a similar issue, where if we do not specify image id in cloud-controller.xml, the instance not spawning in the selected partition. As a fix we can do the following: - When an instance need to be spawned, build a new IaasProvider object with the latest available configurations, and the caching the object in the maps - Consider the following order in building the IaasProvider object: 1. IaaS provider information defined in cloud-controller.xml 2. IaaS provider information defined in cartridge definition This ordering will ensure that any information defined in the cloud-controller.xml can be overridden by information in the cartridge definition. WDYT? [1]. [EC2] Removing the Image Id from CC Results in instances Spinning in Wrong Zones -- Thanks and Regards, Isuru H. +94 716 358 048* <http://wso2.com/>*