[jira] [Resolved] (CLOUDSTACK-6815) CallContext contains incorrect UUID for Account

["Alena Prokharchyk (JIRA)" <ji...@apache.org>]

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

Alena Prokharchyk resolved CLOUDSTACK-6815.
-------------------------------------------

    Resolution: Cannot Reproduce

Mike, I can't reproduce it. I assume you observed the problem in SolidFireSharedPrimaryDataStoreLifeCycle class, createSolidFireVolume method? I couldn't exercise this call, what I did was:

* copy pasted the line below to the StorageManagerImpl, createPool method:
Account csAccount = CallContext.current().getCallingAccount();

Attached the debugger to see what csAccount.getUuid() returns, and it always returned the UUID of the account taken from "cloud.account" table. And it was consistent for the several calls I've executed.

> CallContext contains incorrect UUID for Account
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-6815
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6815
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>         Environment: Ubuntu 12.04
>            Reporter: Mike Tutkowski
>            Assignee: Alena Prokharchyk
>             Fix For: 4.5.0
>
>
> Copy/paste of an e-mail I sent to CloudStack dev@:
> Hi,
> I noticed while executing the createStoragePool command that the following does not work entirely as expected:
> Account csAccount = CallContext.current().getCallingAccount();
> The Account that is returned has the expected name and id, but its UUID is not correct.
> For example, I see the account name of "admin" and an id of "2" (in my case, both are correct); however, the UUID is different each time I run the createStoragePool command.
> I assume the UUID should be what's in the account table for the applicable row, right?
> Anyone have any thoughts on this?
> Thanks!



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