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 (Created) (JIRA)" <ji...@apache.org> on 2011/10/10 19:38:32 UTC
[jira] [Created] (DTACLOUD-91) Broken validation for Range hardware
profile properties
Broken validation for Range hardware profile properties
-------------------------------------------------------
Key: DTACLOUD-91
URL: https://issues.apache.org/jira/browse/DTACLOUD-91
Project: DeltaCloud
Issue Type: Bug
Environment: deltacloud-core < r1181084
Reporter: Michal Fojtik
Assignee: Michal Fojtik
Priority: Critical
Joe found a bug in RHEV-M when he tried to start a new instance he got 400 with validation error message on CPU property.
This was caused by mistake in our validation suite where I used 'value' instead of 'values'. This problem was already fixed.
--
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
[jira] [Resolved] (DTACLOUD-91) Broken validation for Range
hardware profile properties
Posted by "Michal Fojtik (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-91.
-----------------------------------
Resolution: Fixed
Resolved in r1181084
> Broken validation for Range hardware profile properties
> -------------------------------------------------------
>
> Key: DTACLOUD-91
> URL: https://issues.apache.org/jira/browse/DTACLOUD-91
> Project: DeltaCloud
> Issue Type: Bug
> Environment: deltacloud-core < r1181084
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
> Priority: Critical
>
> Joe found a bug in RHEV-M when he tried to start a new instance he got 400 with validation error message on CPU property.
> This was caused by mistake in our validation suite where I used 'value' instead of 'values'. This problem was already fixed.
--
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