Bug 739579
| Summary: | Deployable fails to launch on EC2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Joe Vlcek <jvlcek> | ||||||
| Component: | aeolus-conductor | Assignee: | Angus Thomas <athomas> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, clalance, dajohnso, deltacloud-maint, dgao, dradez, gblomqui, jvlcek, ssachdev | ||||||
| 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: | 2011-10-07 12:50:25 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Hmm, we're missing some info here.. maybe the rails log has a failure in it? The thin log isn't showing anything. There will likely be a traceback in one of the logs dealing with the submission if it failed. Created attachment 524412 [details]
Deltacloud EC2 log with Errors
Deltacloud EC2 log with Errors
The only possibly related log I see with errors is the /var/log/deltacloud-core/ec2.log Which I've attached. Chris Lalancette told me he has made code changes which may address this. I am adding him to the cc-list so he can determine if his changes address what is seen in the newly attached log. condor removed... rechecking Yes, this should be fixed by the updated packages. Instances 3 Properties Graphic ViewFilter View Instances testThree/back IP Address: ec2-107-20-27-153.compute-1.amazonaws.com State: running Download key testThree/frontend IP Address: ec2-184-73-128-223.compute-1.amazonaws.com State: running Download key testThree/middle IP Address: ec2-50-16-6-150.compute-1.amazonaws.com State: running Download key [root@unused ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-all-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-devel-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-configure-2.0.2-4.20110921102958gitcaa9608.fc15.noarch rubygem-aeolus-image-0.1.0-3.20110922120732gita0b9a44.fc15.noarch haha, ya that'll fix it :). |
Created attachment 523848 [details] /var/log/aeolus-conductor/thin.log from failed launch Description of problem: After applying the latest updates attempts to launch a deployable on EC2 fails. Version-Release number of selected component (if applicable): 0.4.0-0.20110916175452git9d14599.fc15 How reproducible: Configure Conductor for EC2, attempt to launch a deployable with at least one "Assembly" with an EC2 "Image ID" Steps to Reproduce: 1.Upgrade to the latest bits from the -testing repo, or build from source 2. Run aeolus-configure 3. Attempt to launch deployable Actual results: /var/log/aeolus-conductor/thin.log seems to indicate the launch happened but the Condor que is empty. keelhaul % condor_q -better Warning: Found no submitters -- Submitter: keelhaul : <10.16.19.204:49471> : keelhaul WARNING: Analysis is only meaningful for Grid universe jobs using matchmaking. keelhaul % Expected results: A Condor Job should show up in the Condor queue The image should be launched on EC2 Additional info: thin.log file attached.