Created attachment 623685 [details] multi-instance Description of problem: lauch multi-assembly deployments with images of 2 different providers fails Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Added Provider accounts for ec2, rhevm and Vsphere 2. Built and Pushed for all the providers together 3. Created an Application Blueprint from this image and launched 4. Actual results: Only one instance is launched according to priority (for me rhevm had 1) Expected results: Three instances should be launched under one application for all the proviuders. Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.13.16-1.el6cf.noarch aeolus-conductor-daemons-0.13.16-1.el6cf.noarch rubygem-aeolus-cli-0.7.3-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.16-1.el6cf.noarch aeolus-conductor-0.13.16-1.el6cf.noarch aeolus-configure-2.8.8-1.el6cf.noarch
Another Scenario : Created Three Separate images for ec2 , rhevm and vsphere and copied the image id of these three into a single xml as shown below : <?xml version="1.0"?> <deployable version="1.0" name="all_img"> <description/> <assemblies> <assembly hwp="small-x86_64" name="rhev-img"> <image id="b16a5506-1170-11e2-9f1b-0023aefc3864"/> </assembly> <assembly hwp="small-x86_64" name="ec2-img"> <image id="56a64d20-1178-11e2-9f1b-0023aefc3864"/> </assembly> <assembly hwp="small-x86_64" name="vsphere-img"> <image id="816a5506-1170-11e2-9f1b-0023aefc3864"/> </assembly> </assemblies> </deployable> But even this doesn't work and launch all the three instances
Will provide an updated error message that this should not be allowed to launch.
Conductor doesn't support launching of cross-provider deployments. Behavior in both comments is as expected. 1) in first case one image was built and pushed to all 3 providers, deployable with this one image was then launched on one provider with highest priority. 2) in second case a deployable contained 3 images and none of the providers contained all 3 images. Error message that deployment can't be launched was displayed on launch overview page. -> closing as not a bug