cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-6583) API:MS: attachVolume fails with could not find account in domain
Date Tue, 06 May 2014 18:49:14 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Min Chen resolved CLOUDSTACK-6583.
----------------------------------

       Resolution: Invalid
    Fix Version/s: 4.4.0

This is working as expected. When both domainId and account are passed to listVirtualMachines
api, it will validate if the account passed belongs to the given domain, if not, it will throw
validation error. In your case, the volume to be attached has mismatched account and domain
information stored due to https://issues.apache.org/jira/browse/CLOUDSTACK-6568, thus causing
this issue.

> API:MS: attachVolume fails with could not find account in domain
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6583
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6583
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Management Server
>    Affects Versions: 4.4.0
>            Reporter: Parth Jagirdar
>            Priority: Critical
>             Fix For: 4.4.0
>
>         Attachments: attachVolume.jpg
>
>
> Observed with Domains and sub-domains.
> List virtual Machine works as expected if invoked for account in the same domain.
> Consider following scenario::
> If Root attempts attach disk on a volume that belongs to his domain, Eligible VM's get
listed.
> If Root attempts attach disk on a volume that belongs to a "sub-domain or other domain",
Eligible VM's "do not get listed and Error is thrown".
> Refer to screen.
> 2014-05-06 10:56:31,420 INFO  [a.c.c.a.ApiServer] (catalina-exec-4:ctx-13cf7c3a ctx-6c641208)
(userId=2 accountId=2 sessionId=79D20423CCD7FD1161C97D8DF82959B6) 10.215.2.19 -- GET command=listVirtualMachines&response=json&sessionkey=bsHjDKTVOfNOzjz4%2Bv%2BoZvHKhJ0%3D&zoneid=05f156b6-cf10-4891-b7d7-6421f4d87e91&domainid=1782af36-9de0-484d-84ea-e525b9661646&account=d11&hypervisor=VMware&state=Running&_=1399398991208
431 could not find account d11 in domain 1782af36-9de0-484d-84ea-e525b9661646
> 2014-05-06 10:56:31,605 INFO  [a.c.c.a.ApiServer] (catalina-exec-24:ctx-3c870648 ctx-7200acbd)
(userId=2 accountId=2 sessionId=79D20423CCD7FD1161C97D8DF82959B6) 10.215.2.19 -- GET command=listVirtualMachines&response=json&sessionkey=bsHjDKTVOfNOzjz4%2Bv%2BoZvHKhJ0%3D&zoneid=05f156b6-cf10-4891-b7d7-6421f4d87e91&domainid=1782af36-9de0-484d-84ea-e525b9661646&account=d11&hypervisor=VMware&state=Stopped&_=1399398991390
431 could not find account d11 in domain 1782af36-9de0-484d-84ea-e525b9661646



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message