You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Justin Clift (JIRA)" <ji...@apache.org> on 2011/08/01 21:29:09 UTC

[jira] [Created] (DTACLOUD-62) Deltacloud isn't passing Cloud specific error codes, needed for the user to identify and solve underlying issues

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: David Lutterkort
            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira