[
https://issues.apache.org/jira/browse/CLOUDSTACK-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938434#comment-13938434
]
ASF subversion and git services commented on CLOUDSTACK-6245:
-------------------------------------------------------------
Commit d4fdc184fe9c6717d2ed4e4fe4c39d9759a90608 in cloudstack's branch
refs/heads/4.3-forward from Edison Su
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d4fdc18 ]
CLOUDSTACK-6245: the security group rule is lagging behind the rules in DB, due
to there is a worker thread launched inside a transaction Reviewed-by: Alex
> Security group rules on hypervisor host are lagging behind rules in DB
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-6245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6245
> 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: edison su
> Assignee: edison su
> Priority: Blocker
> Fix For: 4.3.0
>
>
> Maybe due to the change in DB transaction code, we accidentally start a
> worker thread to program security group rule on hypervisor host, inside a DB
> transaction during add/revoke security group rule. So there is a chance that,
> the work thread is started before the transaction is committed, thus the
> worker thread can't find the newly added rules.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
