Details
-
Bug
-
Status: Resolved
-
Resolution: Duplicate
-
(unspecified)
-
None
-
None
-
Operating System: All
Platform: All
-
7190
Description
Created VM connected to private network (IP 10.0.123.6) and to public network with floating IP (IP 10.64.121.7).
The OF interface for the VM is – as show in ovs-ofctl dump-ports-desc:
6(tap911e0bc7-f0): addr:fe:16:3e:fa:fc:1e
config: 0
state: 0
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
The flow in table 220 is incorrect – the output should’ve been to OF port 6 (instead of 2):
cookie=0x8000007, duration=69648.553s, table=220, n_packets=12987, n_bytes=634746, priority=7,reg6=0xe0000400 actions=output:2
The table 0 flow is correct – with LPORT “4000…”:
cookie=0x8000000, duration=69693.558s, table=0, n_packets=189, n_bytes=20384, priority=4,in_port=6 actions=write_metadata:0x40000000000/0xffffff0000000001,goto_table:17
There was no change done to the VM that we know of (such as reboot/resize/rebuild).
It was created around 18:29.
Also, were created 8 other VMs manually around the same time.
It’s not clear where the OF port 2 came from it does not appear in the dump-ports-desc output.
Attachments
Issue Links
- duplicates
-
NETVIRT-288 OVS egress table (220) contains stale rules that send the packet to the wrong port
- Resolved