Created attachment 568269 [details] DeltaCloud Log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Build and Pushed an image to rhevm from aeolus 2.Tried to lauch instance using it 3.Instance went to "stopped'" state from "Pending" 4.Observed error log in delta cloud 5.No error message on conductor Actual results: Got an exception in deltacloud log /var/log/deltacloud/mock.log Expected results: Should display appropriate error msg " Insufficient memory to lauch the instance" on conductor Additional info: root@intel-d3c69-01 ~]# rpm -qa | grep deltacloud deltacloud-core-vsphere-0.5.0-5.el6.noarch deltacloud-core-rhevm-0.5.0-5.el6.noarch deltacloud-core-0.5.0-5.el6.noarch deltacloud-core-ec2-0.5.0-5.el6.noarch rubygem-deltacloud-client-0.5.0-2.el6.noarch [root@intel-d3c69-01 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-41.el6.noarch aeolus-configure-2.5.0-18.el6.noarch aeolus-conductor-daemons-0.8.0-41.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.0-13.el6.noarch aeolus-all-0.8.0-41.el6.noarch aeolus-conductor-0.8.0-41.el6.noarch ---Note--- A JIRA ticket as been raised for the issue https://issues.apache.org/jira/browse/DTACLOUD-154
This issue should be fixed and reported properly in latest Deltacloud (git).
Hugh, Mike, Wes was questioning if any more deltacloud changes, like this one would make it into this release? QE is pretty sure no more deltacloud changes will be pulled in thus pushing this out post 1.0.
This fix does not appear to be in deltacloud-core-0.5.0-10.el6_2, so we'll need a new build of deltacloud with the patch applied if we want to clear this with 1.1.0.
This rpm won't be revved until 2.0. Moving to 2.0.0? for consideration at that time.