cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6245) Security group rules on hypervisor host are lagging behind rules in DB
Date Mon, 17 Mar 2014 23:42:44 GMT


ASF subversion and git services commented on CLOUDSTACK-6245:

Commit d2bec2e14f3720e944de345b569ee2bfb78f0347 in cloudstack's branch refs/heads/4.3 from
Edison Su
[;h=d2bec2e ]

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
(cherry picked from commit d4fdc184fe9c6717d2ed4e4fe4c39d9759a90608)

Signed-off-by: Animesh Chaturvedi <>

> Security group rules on hypervisor host are lagging behind rules in DB
> ----------------------------------------------------------------------
>                 Key: CLOUDSTACK-6245
>                 URL:
>             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

View raw message