You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/07/31 18:31:53 UTC
[jira] [Closed] (CLOUDSTACK-2477) [GSLB] CloudStack currently
allows admin to map LB rule of one account to GSLB rule of a different
account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru closed CLOUDSTACK-2477.
--------------------------------------------------
Have verified this issue and I dont see this issue any more and moreover, now there is a flexibility for admin to create GSLB rules on behalf of end user. Closing the bug.
2013-07-31 21:43:20,521 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-97 = [ 3c2b541b-a6c1-4a91-93aa-f25b2253bc13 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd
com.cloud.exception.InvalidParameterValueException: GSLB rule and load balancer rule does not belong to same account
at org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:214)
at org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:151)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
> [GSLB] CloudStack currently allows admin to map LB rule of one account to GSLB rule of a different account
> ----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2477
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2477
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have at least 2 non-ROOT domain users (dom1User3 & dom2User1) and ROOT-admin
> 2. As dom1User3, have at least 1 LB rule ex:- zone1LB1
> 3. As dom2User1, create a GSLB rule ex: test
> 4. As ROOT-Admin user, try to add zoneLB1 to "test"
> Observations:-
> (i) It goes fine without any issues.
> (ii) Based on the observations, it is now possible to have one accounts LB rule to be mapped to another GSLB rule.
> Attaching all the required logs to the bug.
--
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