Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 28 Jun 2013 09:11:23 +0000 (UTC)
From: "Abhinav Roy (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12655289.1372410545384.183140.1372410683071@arcas>
In-Reply-To: <JIRA.12655289.1372410545384@arcas>
References: <JIRA.12655289.1372410545384@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-3265) [Health Check for NS LB]Failure
 to create a lb health check policy returns a API response in the UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abhinav Roy updated CLOUDSTACK-3265:
------------------------------------

    Attachment: lb healthchecks.jpg

Attaching the screenshot
                
> [Health Check for NS LB]Failure to create a lb health check policy returns a API response in the UI
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3265
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3265
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.2.0
>            Reporter: Abhinav Roy
>            Assignee: Rajesh Battala
>            Priority: Minor
>             Fix For: 4.2.0
>
>         Attachments: lb healthchecks.jpg
>
>
> Steps:
> ========================
> 1. Create a LB rule with VR as LB provider.
> 2. Attach VMs to the LB rule.
> 3. Create Health check policy for that rule
> Expected behaviour:
> =======================
> 1. Since VR is not the supported provider for LB health checks the policy creation should fail gracefully.
> Observed behaviour:
> ======================
> 1. The policy creation fails as expected but the API response is turned in the UI which should not happen. A proper failure message should be displayed instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira