| Summary: | vsphere instances launched, start on vsphere, but state remain pending | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Steve Reichard <sreichar> | ||||||||||||
| Component: | aeolus-conductor | Assignee: | wes hayutin <whayutin> | ||||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | wes hayutin <whayutin> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 1.0.0 | CC: | akarol, deltacloud-maint, scollier, ssachdev | ||||||||||||
| Target Milestone: | rc | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2011-12-10 21:18:10 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Steve Reichard
2011-12-09 14:49:48 UTC
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
|