Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 835715

Summary: Conductor (installed from Fedora 17) does not pick up when a deployed instance is running (and its IP address)
Product: [Retired] CloudForms Cloud Engine Reporter: Ronelle Landy <rlandy>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: dajohnso
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Instance still pending
none
Deltacloud shows running instance none

Description Ronelle Landy 2012-06-26 22:27:01 UTC 
Created attachment 594625 [details]
Instance still pending

Description of problem:

When running conductor on Fedora 17 (aeolus-conductor-0.10.2-1.fc17.noarch), I built and push an image to vsphere and rhevm. Then I created a deployable and launched the deployable to a realm associated with the vsphere provider.
The instance is launched and after some time starts running and is assigned an IP address (as can be seen when viewing the instance through the provider console or deltacloud) but Conductor never picks up this change in the instance's state and shows the instance as "pending" - no IP address.

See attached screenshots of the instance displayed in Conductor (Pending) and the instance displayed in Deltacloud GUI (running with IP address)


Steps to Reproduce:
1. Install conductor on a F17 machine using testing-updates
2. run aeolus-configure -p admin
3. run aeolus-configure -p mock,rhevm,vsphere
4. run aeolus-restart-services
5. log in to conductor as admin
6. add provider accounts
7. build and push templates to providers (vsphere in this case)
8. create a deployable and launch to an attached realm
9. monitor the provider console or deltaclous to see that the instnace is started and an IP address is assigned (possible to ssh to the instance) (see attached screenshot)
10. see that conductor still shows the instance as "pending"  - no ip address ( see attcahed screenshot)  


Additional info:

rpms installed:

>> rpm -qa |grep aeolus
aeolus-conductor-doc-0.10.2-1.fc17.noarch
rubygem-aeolus-cli-0.5.0-1.fc17.noarch
aeolus-conductor-0.10.2-1.fc17.noarch
aeolus-conductor-daemons-0.10.2-1.fc17.noarch
aeolus-configure-2.6.0-1.fc17.noarch
rubygem-aeolus-image-0.5.0-1.fc17.noarch
aeolus-all-0.10.2-1.fc17.noarch

>> rpm -qa |grep deltacloud
deltacloud-core-rackspace-1.0.0-3.fc17.noarch
deltacloud-core-rimuhosting-1.0.0-3.fc17.noarch
deltacloud-core-gogrid-1.0.0-3.fc17.noarch
deltacloud-core-1.0.0-3.fc17.noarch
deltacloud-core-openstack-1.0.0-3.fc17.noarch
deltacloud-core-sbc-1.0.0-3.fc17.noarch
deltacloud-core-rhevm-1.0.0-3.fc17.noarch
deltacloud-core-google-1.0.0-3.fc17.noarch
deltacloud-core-fgcp-1.0.0-3.fc17.noarch
deltacloud-core-ec2-1.0.0-3.fc17.noarch
deltacloud-core-all-1.0.0-3.fc17.noarch
rubygem-deltacloud-client-0.5.0-3.fc17.noarch
deltacloud-core-doc-1.0.0-3.fc17.noarch
deltacloud-core-vsphere-1.0.0-3.fc17.noarch
deltacloud-core-opennebula-1.0.0-3.fc17.noarch
deltacloud-core-eucalyptus-1.0.0-3.fc17.noarch
Comment 1 Ronelle Landy 2012-06-26 22:27:51 UTC 
Created attachment 594626 [details]
Deltacloud shows running instance