Security group assigned to existing vm does not create flows

Opendaylight Boron, odl-ovsdb-openstack in use, no L3 (ovsdb.l3.fwd.enabled=no), OpenStack Mitaka, networking-odl_v2

Scenario:

Create VM, create Security group:
{
"rules": "id='8e77f8c1-0de0-4f3e-9f76-171fbe241f90', ip_protocol='tcp', ip_range='0.0.0.0/0', port_range='22:22'\nid='cd1bc019-2c6f-443c-8662-b3c6e5cd02ec', ip_protocol='icmp', ip_range='0.0.0.0/0'",
"project_id": "9eea32b513954dfba3244bccc4316e12",
"description": "Security group for vPing test case",
"name": "vPing-sg",
"id": "f807fc7a-ea76-49df-9261-4b19c70b0917"
}

assign SG to VM

Result:

Flows which should allow communication on port 22 are not created.

Workaround:

Assign SG during vm creation. Related change in opnfv: https://gerrit.opnfv.org/gerrit/#/c/23637/