venkata swamybabu budumuru created CLOUDSTACK-4392:
------------------------------------------------------

             Summary: [listvolumesresponse] shouldn't show primary storage 
information if the listVolumes API is fired by non-ROOT domain user
                 Key: CLOUDSTACK-4392
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4392
             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: commit id # 3c40e8bb3f6278f78c24c6317d513bd5ad599944
            Reporter: venkata swamybabu budumuru
             Fix For: 4.2.0


Steps to reproduce:

1. Have at least one advanced zone with KVM cluster
Note : In my case I have added a cluster wide primary storage with name 
"primary"
2. Login as non-ROOT domain user and deploy a VM
3. Go to Storage and select the ROOT volume

Observations:

i. UI doesn't show any primary info for non-ROOT domain user but, API is still 
showing the primary storage information.

_       1376896572585
command listVolumes
id      f990b522-ce34-451b-8613-97666618038a
response        json
sessionkey      VzRdBK6XYh5q+mW2lwdKt347FuM=

{ "listvolumesresponse" : { "count":1 ,"volume" : [  
{"id":"f990b522-ce34-451b-8613-97666618038a","name":"ROOT-3","zoneid":"17b46f24-47fe-4346-be8d-800987ce5bb2","zonename":"zone1","type":"ROOT","deviceid":0,"virtualmachineid":"8e057275-1575-46b4-b9c2-232ac16c2c5c","vmname":"VM1","vmdisplayname":"VM1","vmstate":"Running","size":8589934592,"created":"2013-08-19T12:39:48+0530","state":"Ready","account":"dom1Acc1","domainid":"24e40c47-8595-4d23-8015-2e624ee45f4a","domain":"dom1","storagetype":"shared","storage":"Priimary1","destroyed":false,"serviceofferingid":"9f5b96af-c82b-4110-93cb-2aceee5e3a24","serviceofferingname":"Small
 Instance","serviceofferingdisplaytext":"Small 
Instance","isextractable":true,"tags":[],"displayvolume":false} ] } }


Attaching all the logs along with db dump 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

Reply via email to