[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552900#comment-14552900
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8231:
--------------------------------------------

GitHub user vadimkim opened a pull request:

    https://github.com/apache/cloudstack/pull/271

    CLOUDSTACK-8231: Fixed UI empty drop-down list for LB rules

    It seems that getLbAlgorithms() function must be called if context is 
"undefined".  If context is defined then function returns empty list. That is 
why drop-down menu is also empty when I add new LB rule.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vadimkim/cloudstack master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/271.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #271
    
----
commit 7ee9b1042f35a2998217d973b5ee447ca68497fb
Author: Vadim Kimlaychuk <[email protected]>
Date:   2015-05-20T19:08:29Z

    CLOUDSTACK-8231: Fixed UI empty drop-down list for LB rules

----


> Fail to create load-balancing service on VPC
> --------------------------------------------
>
>                 Key: CLOUDSTACK-8231
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>    Affects Versions: 4.5.0
>            Reporter: Pierre-Luc Dion
>            Assignee: Rohit Yadav
>            Priority: Critical
>             Fix For: 4.6.0, 4.5.2
>
>         Attachments: lb-algo.png
>
>
> Using the uI, cannot create Load-Balancing rules on a VPC tier because the 
> load-balancing algorithm  is empty and the drop down display nothing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to