cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2343) [GSLB] listGlobalLoadBalancerRules shouldn't list the globalGSLBRules of other accounts
Date Mon, 06 May 2013 13:50:15 GMT
venkata swamybabu budumuru created CLOUDSTACK-2343:
------------------------------------------------------

             Summary: [GSLB] listGlobalLoadBalancerRules shouldn't list the globalGSLBRules
of other accounts
                 Key: CLOUDSTACK-2343
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2343
             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


Steps to reproduce :

1. Have CloudStack setup with at least 2 zones
2. Have at least 2 account as mentioned below

* dom1/dom1Acc1/dom1User3
* dom2/dom2Acc1/dom2User1

3. Login as dom1User3 create a globalLoadBalancerRule and assign at least 2 load balancer
rules.
4. Login as dom2User3 and try to list GSLBRules

Observations:

(i) it lists the GSLB rules created by dom1User3. 

Attaching the snapshot of the screen.

(ii) Here is the API response
{ "listgloballoadbalancerrulesresponse" : { "count":1 ,"globalloadbalancerrule" : [  {"id":"62054a73-4598-4e9e-a299-c28ed3227c78","name":"test","description":"test","gslbdomainname":"test","gslblbmethod":"roundrobin","gslbstickysessionmethodname":"sourceip","gslbservicetype":"tcp","regionid":1,"account":"dom1Acc3","domainid":"01ceec9f-6c57-4785-a20b-6c43a82a12b4","domain":"dom1","loadbalancerrule":[{"id":"9b5267df-eaf5-41ae-bc46-dc61fa5e9024","name":"Zone1LB1","publicipid":"132b830e-b8b9-48f3-8ccd-cb2f572cd3de","publicip":"10.147.44.61","publicport":"22","privateport":"22","algorithm":"roundrobin","cidrlist":"","account":"dom1Acc3","domainid":"01ceec9f-6c57-4785-a20b-6c43a82a12b4","domain":"dom1","state":"Active","zoneid":"733ee102-6ad1-469b-839d-ae35250bc0f4","tags":[]},{"id":"50b0cb8e-2d26-4f95-a1fb-bd4dde50db21","name":"Zone2Lb1","publicipid":"d94f8dec-ccf5-4be2-b9c8-054be6da6e19","publicip":"10.147.54.161","publicport":"22","privateport":"22","algorithm":"roundrobin","cidrlist":"","account":"dom1Acc3","domainid":"01ceec9f-6c57-4785-a20b-6c43a82a12b4","domain":"dom1","state":"Active","zoneid":"f75058e6-5c25-41b2-841e-6c5b62ac07bf","tags":[]}]}
] } }

attaching all the required logs along with db dump.

--
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

Mime
View raw message