You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/05/06 09:50:16 UTC
[jira] [Closed] (CLOUDSTACK-1849) [AWS Style Health Checks]
Creation of LB Health Check policy fails if the value of "Unhealthy
Threshold" parameter is 3 or more.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinav Roy closed CLOUDSTACK-1849.
-----------------------------------
Closing the bug after verifying the fix with the latest master build
> [AWS Style Health Checks] Creation of LB Health Check policy fails if the value of "Unhealthy Threshold" parameter is 3 or more.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1849
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1849
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: 4.2.0
> Environment: Netscaler - 10.x
> CS build : Master
> Reporter: Abhinav Roy
> Assignee: Rajesh Battala
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps :
> =======================
> 1. Deploy CS Advanced zone setup
> 2. Create a guest network with NS offering.
> 3. Now create a LB rule, add VMs to the rule.
> 4. Create a health check policy with unhealthy threshold = 3 or 4 or 5 ...........
> Expected Behaviour :
> ======================
> The health check policy should be create successfully.
> Observed behaviour :
> ======================
> The policy creation fails with " monitor retries should be greater than monitor failure retries " ..........
> Reason :
> ------------------
> When we create a health check policy on a LB rule , a corresponding monitor is created on NS .
> Creation of monitor involves paasing of values for parameters , success retries , failure retries and retries.
> Now success retries is mapped to healthy threshold
> failure retries is mapped to unhealthy threshold
> but we never change the value of "retires" parameter , it always has a default value which is 3.
> but the value of this parameter should always be greater than unhealthy threshold value for creation of a monitor/health check policy.
> So, whenever we try to create a policy/monitor with unhealthy threshold/failure retries value 3 or more , it fails.
> Solution :
> ----------------
> Make sure that the vaule of retries is always greater than the value of failure retries.
--
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