[Mainline-Build 2704]: one flow is stuck and never deleted

Bug #1538661 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
New
High
Naveen N

Bug Description

one of the reverse flow is stuck with Action F-

   403484<=>458048 2002:1::6:9002 6 (1)
                         2002:2::3:10002
    (K(nh):34, Action:F, Flags:, TCP:Sr, S(nh):34, Statistics:0/0 UdpSrcPort 64185

for sometime I saw forward flow in HOLD state(but unlinked with reverse flow) and deleted after sometime(may be flow aged out):

   403484<=>458048 2002:1::6:9002 6 (1)
                         2002:2::3:10002
    (K(nh):34, Action:F, Flags:, TCP:Sr, S(nh):34, Statistics:0/0 UdpSrcPort 64185

   450272 :::0 0 (1)
                         :::0
    (K(nh):0, Action:D(Unknown), Flags:E, S(nh):0, Statistics:5/371 UdpSrcPort 0

   458048 2002:2::3:10002 6 (1)
                         2002:1::6:9002
    (K(nh):34, Action:H, Flags:, TCP:S, S(nh):0, Statistics:17/1360 UdpSrcPort 0

root@nodec62:~# flow -l --show-evicted | grep 458048 -A3 ------> grep with HOLD flow index(which got deleted after sometime)
   403484<=>458048 2002:1::6:9002 6 (1)
                         2002:2::3:10002
    (K(nh):34, Action:F, Flags:, TCP:Sr, S(nh):34, Statistics:0/0 UdpSrcPort 64185

test steps:
test was to try to create tcp session to non-existing port(reset will be sent from other end) in loop.

on VM 2002:2::3 ran below cmd:
"while true;do echo hi | nc -6 2002:1::6 9002 -p 10002 -vv -q 2000;done"

Revision history for this message
alok kumar (kalok) wrote :

setup Info :

env.roledefs = {
    'all': [host1,host2,host3,host4],
    'cfgm': [host1],
    'openstack':[host2],
    'control': [host1,host2],
    'compute': [host3,host4],
    'collector': [host1,host2],
    'webui': [host1],
    'database': [host1],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodec64', 'nodeg18', 'nodec62', 'nodec12']

Revision history for this message
alok kumar (kalok) wrote :

one more flow to the existing port 22 in HOLD state -

root@nodec12:~# flow -l --show-evicted | grep 2002:2::3 -A2 -B2 | grep 2002:1::6 -A2 -B2

   388832 2002:2::3:10002 6 (3)
                         2002:1::6:22
    (K(nh):56, Action:H, Flags:, TCP:S, S(nh):0, Statistics:6/564 UdpSrcPort 0

alok kumar (kalok)
tags: added: blocker
Revision history for this message
alok kumar (kalok) wrote :

3 new flows stuck. This happened when Fat flow was added for TCP port 22 and remains forever even when Fat flow config is removed.

root@nodec12:~# flow -l --show-evicted| grep :22 -A2 -B1

   192316<=>289976 1.1.1.4:22 6 (1)
                         1.1.1.3:0
    (K(nh):21, Action:D(Unknown), Flags:, TCP:Sr, S(nh):21, Statistics:0/0 UdpSrcPort 55055
--

   220516<=>394524 1.1.1.3:22 6 (1)
                         1.1.1.2:33519
    (K(nh):16, Action:F, Flags:, TCP:, S(nh):16, Statistics:4/904 UdpSrcPort 52355
--

   384220<=>86728 1.1.1.4:22 6 (1)
                         1.1.1.2:44004
    (K(nh):21, Action:F, Flags:, TCP:, S(nh):21, Statistics:9/594 UdpSrcPort 55335

Revision history for this message
alok kumar (kalok) wrote :

1 more flow stuck with HOLD state.this is also with Fat flow.

root@nodec12:~# flow -l --show-evicted| grep Action:H -B2
   222136 1.1.1.4:22 6 (1)
                         1.1.1.3:36667
    (K(nh):21, Action:H, Flags:, TCP:F, S(nh):0, Statistics:9/594 UdpSrcPort 0

alok kumar (kalok)
information type: Proprietary → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.