[ https://issues.apache.org/jira/browse/CLOUDSTACK-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235550#comment-14235550 ]
Rohit Yadav commented on CLOUDSTACK-5358: ----------------------------------------- [~kelveny] code paths have changed a lot between 4.3-4.4, 4.4-4.5/master. Can we get a detailed information of how sync on object is broken and the job framework how it related to APIs. > API: synchronization on the object is broken > -------------------------------------------- > > Key: CLOUDSTACK-5358 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5358 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.3.0 > Reporter: Alena Prokharchyk > Assignee: Kelven Yang > Priority: Critical > Fix For: Future > > > There is a way to synchronize API commands on certain CS object. For example, > when createFirewallRule is called, synchronization on the Network is being > done, so the next command won't be processed till the last one is executed. > To enable it for the certain command, following methods have to be added to > corresponding *Cmd class: > @Override > public String getSyncObjType() { > return BaseAsyncCmd.networkSyncObject; > } > @Override > public Long getSyncObjId() { > return getIp().getAssociatedWithNetworkId(); > } > This logic got broken after the changes for vmSync got merged in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)