You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/16 16:28:41 UTC
[jira] [Resolved] (DTACLOUD-126) RHEV-M: We need to skip 'default'
cluster when no 'realm_id' is specified in create_instance
[ https://issues.apache.org/jira/browse/DTACLOUD-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-126.
------------------------------------
Resolution: Fixed
This issue should be fixed in r1231960
> RHEV-M: We need to skip 'default' cluster when no 'realm_id' is specified in create_instance
> --------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-126
> URL: https://issues.apache.org/jira/browse/DTACLOUD-126
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
> Priority: Blocker
> Attachments: 0001-RHEV-M-Choose-the-image-realm-when-no-realm-is-being.patch
>
>
> When there is no realm_id provided upon creating a new instance, by default Deltacloud will choose the first 'realm' returned by 'realms' call.
> In RHEV-M it usually means that the 'default' cluster is being returned, which is wrong in most cases, since this cluster is being used for
> holding the 'Blank' template, thus cannot be removed. This cluster usually don't have 'storage domain' assigned and deploying an instance
> there lead to error.
> The solution could to to 'skip' default realm and try to use next realm in row (if there is next realm). If there is just 'default' realm, we should
> choose this realm and additionally give client decent error :-)
--
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