[NETVIRT-215] Security group assigned to existing vm does not create flows Created: 25/Oct/16 Updated: 09/Mar/18 Resolved: 09/Mar/18 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Michal Skalski | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 7021 |
| Description |
|
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: 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/ |
| Comments |
| Comment by Michal Skalski [ 25/Oct/16 ] |
|
Attachment fail-karaf.log has been added with description: SG assigned to existing vm - flows not created |
| Comment by Michal Skalski [ 25/Oct/16 ] |
|
Attachment work-karaf.log has been added with description: SG assigned during vm creation - flows created |
| Comment by Michal Skalski [ 25/Oct/16 ] |
|
When switch to networking-odl v1 (mechanism_driver = 'opendaylight' vs 'opendaylight_v2') assign SG to existing VM generate appropriate flows. However Beryllium was also tested with opendaylight_v2 and that combination was ok. |
| Comment by Sam Hague [ 09/Mar/18 ] |
|
Legacy NetVirt is deprecated. |