[R3.0-2715]: some flows stuck forever with Action:D after agent restart,

Bug #1549104 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
Fix Committed
Undecided
Prabhjot Singh Sethi
Trunk
Fix Committed
Undecided
Prabhjot Singh Sethi

Bug Description

Some of the flows are stuck with Deny action. (NoDstRt)

root@nodec12:~# flow -l
Flow table(size 68157440, entries 532480)

Entries: Created 65959 Added 65931 Processed 65959 Used Overflow entries 0
(Created Flows/CPU: 16664 17032 15632 16631)(oflows 0)

Action:F=Forward, D=Drop N=NAT(S=SNAT, D=DNAT, Ps=SPAT, Pd=DPAT, L=Link Local Port)
 Other:K(nh)=Key_Nexthop, S(nh)=RPF_Nexthop
 Flags:E=Evicted, Ec=Evict Candidate, N=New Flow, M=Modified
TCP(r=reverse):S=SYN, F=FIN, R=RST, C=HalfClose, E=Established, D=Dead

    Index Source:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
    15240<=>152292 2.2.2.3:29 17 (2)
                         1.1.1.3:29
(Gen: 35, K(nh):16, Action:D(NoDstRt), Flags:, S(nh):16, Stats:14/588, SPort 52766)

   101068<=>70980 1.1.1.3:4640 17 (1)
                         2.2.2.3:4640
(Gen: 34, K(nh):11, Action:D(NoDstRt), Flags:, S(nh):11, Stats:14/588, SPort 60068)

   213056<=>249104 1.1.1.3:4638 17 (1)
                         2.2.2.3:4638
(Gen: 1, K(nh):11, Action:D(NoDstRt), Flags:, S(nh):11, Stats:14/588, SPort 51822)

   301248<=>355536 1.1.1.3:4639 17 (1)
                         2.2.2.3:4639
(Gen: 1, K(nh):11, Action:D(NoDstRt), Flags:, S(nh):11, Stats:14/588, SPort 54530)

   311716<=>347460 2.2.2.3:28 17 (2)
                         1.1.1.3:28
(Gen: 18, K(nh):16, Action:D(NoDstRt), Flags:, S(nh):16, Stats:14/588, SPort 52091)

   453744<=>286816 1.1.1.3:4641 17 (1)
                         2.2.2.3:4641
(Gen: 46, K(nh):11, Action:D(NoDstRt), Flags:, S(nh):11, Stats:14/588, SPort 60554)

This happened when I restarted agent while live traffic was there.
before agent restart, I had changed aging timeout from 60 sec to 180 sec.

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
Hari Prasad Killi (haripk) wrote :
alok kumar (kalok)
information type: Proprietary → Public
Revision history for this message
Prabhjot Singh Sethi (prabhjot) wrote :
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.