[
https://issues.apache.org/jira/browse/DTACLOUD-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-62.
---------------------------------
Resolution: Fixed
Referring to comments in https://bugzilla.redhat.com/show_bug.cgi?id=743676,
Delatcloud is now passing on cloud-specific error. In particular, in the case
of an 'unavailable' or 'invalid' EC2 Availability Zone, Deltacould and
subsequently Conductor will return:
Warnings
Failed to launch following component blueprints:
Errors
500 : Unhandled exception or status code (<availability zone> temporarily
unavailable: (getaddrinfo: Name or service not known))
The fact that this exception is 'unhandled' is another problem ... to be
addressed in another JIRA or other report)
rpm -qa |grep deltacloud
rpm -qa |grep aeolus
deltacloud-core-vsphere-0.5.0-5.el6.noarch
deltacloud-core-ec2-0.5.0-5.el6.noarch
deltacloud-core-rhevm-0.5.0-5.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
[root@hp-dl360g5-02 workspace]# \rpm -qa |grep aeolus
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
> Deltacloud isn't passing Cloud specific error codes, needed for the user to
> identify and solve underlying issues
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-62
> URL: https://issues.apache.org/jira/browse/DTACLOUD-62
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: RHEL 6.1, Aeolus 0.3.0 rpms, EC2
> Reporter: Justin Clift
> Assignee: Michal Fojtik
> Priority: Critical
>
> Sometimes when using EC2 (and potentially other Cloud Providers), starting an
> instance fails because EC2 have decided not to support some aspect of the
> launch configuration. (ie the Availability Zone that was asked for, which
> used to work, but no longer does)
> When this happens, Deltacloud doesn't catch the underlying problem, nor
> report it in an identifiable way so the user can be informed. (ie of action
> they need to take in order to get things working)
> There is an open BZ in Red Hat's Bugzilla, showing the problem this causes
> Aeolus users:
> https://bugzilla.redhat.com/show_bug.cgi?id=717987
> Spontaneous instance startup failure, through no fault of the user nor
> application. And which can be permanent in nature unless the user takes
> Cloud provider specific action. :(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
