Hide Forgot
Description of problem: During testing of imports, When I launched the VM I imported from vsphere I could see it start on the vshpere console but conductor reported it was still pending after several hour. here is the import: [root@cf-cloudforms9 ~]# aeolus-cli import --provider vsphere --target vsphere --description '<image><name>vshpere-spr</name></image>' --id spr Image: c2ca7fb6-19ba-4bdb-9136-76ea53b88713 Build: 5b1bcb89-5dc5-4f44-95ac-ffdf777630c9 Target Image: 914abd37-0632-4a95-b01e-fe59e6b1bcac Provider Image: 6af51c39-b758-4d00-9eb0-9d8e71cdf318 Status: COMPLETE [root@cf-cloudforms9 ~] Here is the deployable: <deployable name="spr_deploy"> <description>This is a spr deployment</description> <assemblies> <assembly name="spr_asmbly" hwp="hwp1"> <image id="c2ca7fb6-19ba-4bdb-9136-76ea53b88713"> </image> </assembly> </assemblies> </deployable> On another launch of the same import images, as part of reproducing for this BZ, the VM launched and the status remained pending (only waited a few minute at this point. Then I built, pushed and launched a RHEL61 instance, same issue, Attached is s screen shot of the status and a tar of logs. Version-Release number of selected component (if applicable): [root@cf-cloudforms9 ~]# /pub/scripts/post_install_configuration_scripts/cf-versions Red Hat Enterprise Linux Server release 6.1 (Santiago) Linux cf-cloudforms9.cloud.lab.eng.bos.redhat.com 2.6.32-131.17.1.el6.x86_64 #1 SMP Thu Sep 29 10:24:25 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux postgresql-8.4.9-1.el6_1.1.x86_64 mongodb-1.8.0-6.el6.x86_64 euca2ools-1.3.1-4.el6_0.noarch ruby-1.8.7.299-7.el6_1.1.x86_64 rubygems-1.8.10-1.el6.noarch deltacloud-core-0.4.1-8.el6.noarch rubygem-deltacloud-client-0.4.0-3.el6.noarch package libdeltacloud is not installed hail-0.8-0.2.gf9c5b967.el6_0.x86_64 puppet-2.6.6-1.el6_0.noarch aeolus-configure-2.3.0-1.el6.noarch iwhd-1.0-1.el6.x86_64 imagefactory-0.8.9-1.el6.noarch aeolus-conductor-daemons-0.6.0-3.el6.noarch aeolus-conductor-0.6.0-3.el6.noarch [root@cf-cloudforms9 ~]# How reproducible: For this installation, so far every attempt. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 544580 [details] logs
Created attachment 544581 [details] screen shot of 1 VM's pending status
Created attachment 544584 [details] screen shot of all vsphere instance with no running status
Created attachment 544586 [details] screenshot of vsphere client with teh 3 instances running
Just launched an ec2 instance that euca is reported running, but conductor has not after several minutes. Interesting, I have a RHEV instance that is reporting the correct state.
try again w/o --description
Created attachment 544986 [details] ss [root@qeblade30 ~]# aeolus-cli import --provider vsphere --target vsphere --id factory-image-98f9c9fb-1eac-4232-8968-9e58961256c4 Image: 7112cf12-92fb-4d2c-9601-809c055ea188 Build: 955e0501-bb22-4b7d-a792-b40d159256a2 Target Image: 7ecead6d-b688-4693-b58e-cd6af4ff8666 Provider Image: e8b08e8f-e7d3-4fa4-bc74-d79e5e732770 Status: COMPLETE [root@qeblade30 ce]# cat vsphereImport.xml <deployable name='vsphere-import'> <description>auto description</description> <assemblies> <assembly name='testVsphere' hwp='default'> <image id='7112cf12-92fb-4d2c-9601-809c055ea188' /> </assembly> </assemblies> </deployable> [root@qeblade30 ce]# [root@qeblade30 ce]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.7.0-4.el6.noarch aeolus-conductor-doc-0.7.0-4.el6.noarch rubygem-aeolus-cli-0.2.0-3.el6.noarch rubygem-aeolus-image-0.2.0-1.el6.noarch aeolus-all-0.7.0-4.el6.noarch aeolus-configure-2.4.0-3.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch