[NETVIRT-127] floating IP NAT default rule sometimes missing when creating a router connected to ext-GW Created: 09/Sep/16 Updated: 20/Sep/16 Resolved: 20/Sep/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Koby Aizer | Assignee: | Koby Aizer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6677 |
| Description |
|
It seems that sometimes when creating a router connected to the external GW, the default rule from 21->26 is not created. This causes floating IP functionality for this specific router not to work. In the rules below, you can see that the default rule for vpnId=0x222e0 is missing the default rule. (0x222f0 is a router that was created correctly, and 0x222e2 is the external network vpnId, which shouldn't have this rule): cookie=0x8000003, duration=244905.117s, table=21, n_packets=22, n_bytes=4622, priority=42,ip,metadata=0x222e0/0xfffffffe,nw_dst=10.0.123.2 actions=write_actions(group:150000) There are not exceptions seen the log. Pretty much reproduces for me in a single node environment when running tempest scenario test tempest.scenario.test_minimum_basic.TestMinimumBasicScenario |
| Comments |
| Comment by Koby Aizer [ 10/Sep/16 ] |
|
This bug seems to happen when you create a router associated with an external network on creation. Devstack & some of the tempest test are configuring it that way. |
| Comment by Alon Kochba [ 13/Sep/16 ] |
| Comment by Alon Kochba [ 13/Sep/16 ] |