Bug 906445
| Summary: | Failed launch logs two different failures in instance history, only one correct | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Aaron Weitekamp <aweiteka> | ||||||
| Component: | aeolus-conductor | Assignee: | Angus Thomas <athomas> | ||||||
| Status: | CLOSED EOL | QA Contact: | Rehana <aeolus-qa-list> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.1.0 | ||||||||
| 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: | 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: |
|
||||||||
Created attachment 691076 [details]
rails.log
|
Created attachment 691074 [details] instance_history_logging Description of problem: I launched to EC2 but there was a networking problem (no route to host). Instance history recorded Version-Release number of selected component (if applicable): 1.1.2 candidate [root@qeblade40 ~]# rpm -qa |grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.8.11-1.el6cf.noarch aeolus-conductor-doc-0.13.26-1.el6cf.noarch aeolus-conductor-0.13.26-1.el6cf.noarch aeolus-all-0.13.26-1.el6cf.noarch aeolus-conductor-daemons-0.13.26-1.el6cf.noarch rubygem-aeolus-cli-0.7.7-1.el6cf.noarch How reproducible: always Steps to Reproduce: 1. create networking problem to provider using firewall or similar 2. attempt launch to provider Expected results: Log only actual cause of failure ACTUAL RESULTS from Instance History (see attached screenshot): 30-Jan-2013 16:50:50: Attempting to launch this deployment on provider account ec2-eu-west-1 [ CORRECT ] 30-Jan-2013 16:50:54: Instance rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: No route to host - connect(2) 30-Jan-2013 16:50:54: Instance rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server state changed to create_failed 30-Jan-2013 16:50:54: State changed to rollback_in_progress 30-Jan-2013 16:50:54: State changed to rollback_complete 30-Jan-2013 16:50:54: State changed to pending [ INCORRECT ] 30-Jan-2013 16:50:57: Failed to launch deployment : Match not found: rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: ec2-ap-northeast-1: Frontend Cloud Resource Cluster ec2-eu-west-1 is not mapped to an applicable Cloud Resource Provider or Provider Realm, rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: ec2-sa-east-1: Frontend Cloud Resource Cluster ec2-eu-west-1 is not mapped to an applicable Cloud Resource Provider or Provider Realm, rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: ec2-us-east-1: Frontend Cloud Resource Cluster ec2-eu-west-1 is not mapped to an applicable Cloud Resource Provider or Provider Realm, rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: ec2-us-west-1: Frontend Cloud Resource Cluster ec2-eu-west-1 is not mapped to an applicable Cloud Resource Provider or Provider Realm, rhel-x86-64-6Server-Public-EC2/rhel-x86-64-6Server: ec2-ap-southeast-1: Frontend Cloud Resource Cluster ec2-eu-west-1 is not mapped to an applicable Cloud Resource Provider or Provider Realm 30-Jan-2013 16:50:57: State changed to failed