You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "chris snow (JIRA)" <ji...@apache.org> on 2014/06/28 13:49:25 UTC

[jira] [Updated] (STRATOS-692) SM configuration errors should be more informative allowing users to resolve their issues

     [ https://issues.apache.org/jira/browse/STRATOS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

chris snow updated STRATOS-692:
-------------------------------

    Description: 
The errors don't allow users to diagnose what actually went wrong.

For example when trying to deploy the following partition...

{code}
{
      "id": "zone-1",
      "provider": "openstack",
      "property": [
          {
            "name": "region",
            "value": "PHX"
          }
 	{
            "name": "zone",
            "value": "PHX01"
          }
      ]
 }
{code}

.. the output received was:

{code}
Invalid Partition Detected : zone-1
{code}

This error doesn't help the user resolve the issue.  Ideally, the error message should give the exact cause of the error:

{code}
Invalid Partition Detected : zone-1
Unknown region: PHX
{code}

If it isn't possible to get the actual error (for example if jclouds doesn't provide it), we could tell the user where they need to look to resolve the problem:

{code}
Invalid Partition Detected : zone-1
Please see the Stratos log file for more information.
{code}

  was:
The errors don't allow users to diagnose what actually went wrong.

For example when trying to deploy the following partition...

{code}
{
      "id": "zone-1",
      "provider": "openstack",
      "property": [
          {
            "name": "region",
            "value": "PHX"
          }
 	{
            "name": "zone",
            "value": "PHX01"
          }
      ]
 }
{code}

.. the output received was:

{code}
Invalid Partition Detected : zone-1
{code}

This error doesn't help the user resolve the issue.  Ideally, the error message should give the exact cause of the error, but if that isn't possible, potentially we could output:

{code}
Invalid Partition Detected : zone-1
Please see the Stratos log file for more information.
{code}


> SM configuration errors should be more informative allowing users to resolve their issues
> -----------------------------------------------------------------------------------------
>
>                 Key: STRATOS-692
>                 URL: https://issues.apache.org/jira/browse/STRATOS-692
>             Project: Stratos
>          Issue Type: Sub-task
>          Components: Stratos Manager
>            Reporter: chris snow
>
> The errors don't allow users to diagnose what actually went wrong.
> For example when trying to deploy the following partition...
> {code}
> {
>       "id": "zone-1",
>       "provider": "openstack",
>       "property": [
>           {
>             "name": "region",
>             "value": "PHX"
>           }
>  	{
>             "name": "zone",
>             "value": "PHX01"
>           }
>       ]
>  }
> {code}
> .. the output received was:
> {code}
> Invalid Partition Detected : zone-1
> {code}
> This error doesn't help the user resolve the issue.  Ideally, the error message should give the exact cause of the error:
> {code}
> Invalid Partition Detected : zone-1
> Unknown region: PHX
> {code}
> If it isn't possible to get the actual error (for example if jclouds doesn't provide it), we could tell the user where they need to look to resolve the problem:
> {code}
> Invalid Partition Detected : zone-1
> Please see the Stratos log file for more information.
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)