[
https://issues.apache.org/jira/browse/CLOUDSTACK-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898846#comment-15898846
]
ASF GitHub Bot commented on CLOUDSTACK-9198:
--------------------------------------------
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1278
@rafaelweingartner, Basically CallContext.current().getCallingAccount(); is
setting the proper context which is later used. If you have observed in code
all the api calls have a similar call before proceeding further. One random
example:
```java
@ActionEvent(eventType = EventTypes.EVENT_VOLUME_UPLOAD, eventDescription
= "uploading volume", async = true)
public VolumeVO uploadVolume(UploadVolumeCmd cmd) throws
ResourceAllocationException {
Account caller = CallContext.current().getCallingAccount();
```
For more details refer
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+CallContext and
commits 7928963 and 11e1e58 which I have mentioned earlier.
Hopefully this clears your doubts.
> VR gets created in the disabled POD
> -----------------------------------
>
> Key: CLOUDSTACK-9198
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9198
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Anshul Gangwar
> Assignee: Anshul Gangwar
>
> VR gets created in the disabled POD
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
