[
https://issues.apache.org/jira/browse/CLOUDSTACK-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843869#comment-13843869
]
ASF subversion and git services commented on CLOUDSTACK-5431:
-------------------------------------------------------------
Commit bd238ce24ecd8a5c9143f2c8b3dc395b26b91c72 in branch refs/heads/master
from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bd238ce ]
CLOUDSTACK-5431: permit 'http' as service type for GSLB rule
> permit 'http' as service type for GSLB rule
> -------------------------------------------
>
> Key: CLOUDSTACK-5431
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5431
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Fix For: 4.3.0
>
>
> For the load balancer rules, LB rule supports TCP/UDP only from API but, when
> load balancer config is configured on the lb provider, implicitly protocol is
> set as HTTP if port is 80. GSLB rules accept only TCP & UDP as service type.
> There will be mismatch when GSLB rule is configured as service type TCP and
> LB rules participating in GSLB are configured to be HTTP.
> On NetScaler in such situation configuring GSLB rule fails with " “Failed to
> created service: xxx cloudsite2 due to Service type mismatch with existing
> service/vserver"
> This bug is to allow 'http' as service type for GSLB rule, so that service
> types of gslb rule and lb rule can be matched.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
