[R3.0-2722]: TCP flows are not deleted as per flow aging configuration

Bug #1551201 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
Medium
Ashok Singh
Trunk
Fix Committed
Medium
Ashok Singh

Bug Description

now after tcp eviction changes bug https://bugs.launchpad.net/juniperopenstack/+bug/1550759, TCP flows are not deleted after aging timeout.

steps:
- aging timeout configured: 5 sec.
- ssh from any VM to other VM and keep the session active without any traffic.
- corresponding flow should be deleted after 5 sec.

the flow is only getting deleted after 3 mins.

Tags: vrouter
alok kumar (kalok)
tags: added: blocker
Revision history for this message
Ashok Singh (ashoksr) wrote :

Aging configuration should be changed via flow_cache_timeout of contrail-vrouter-agent.conf file. The test-case mentioned in the bug is modifying aging configuration via introspect http://compute:8085/Snh_FlowAgeTimeReq?new_age_time=100. When it is modified via introspect agent updates aging time only for default flow-stats-collector and not for flow-stats-collector created for TCP flows

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

hitting this issue only when aging timeout is changed through introspect.
removing blocker tag for now.

tags: removed: blocker
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.0

Review in progress for https://review.opencontrail.org/18101
Submitter: Ashok Singh (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/18101
Committed: http://github.org/Juniper/contrail-controller/commit/54becf8482dfcdcc3a2180f4cf4ff348c815bfbc
Submitter: Zuul
Branch: R3.0

commit 54becf8482dfcdcc3a2180f4cf4ff348c815bfbc
Author: Ashok Singh <email address hidden>
Date: Wed Mar 2 02:35:03 2016 -0800

Update Aging time for TCP flow-stats-collector

When aging time is changed via introspect it was updated only for
default flow-stats-collector. We need to update the aging time for
implicitly added TCP flow-stats-collector as well. However this
update should not be done when TCP flow-stats-collector is configured
explicitly via configuration (Protocol based aging config)

Change-Id: Ic83868fbce82c9c5d5070bd3eb669903f23ee147
Closes-Bug: #1551201

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/18213
Submitter: Ashok Singh (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/18213
Committed: http://github.org/Juniper/contrail-controller/commit/257b512b3eb078c9874e7ec370c4685f6593fce8
Submitter: Zuul
Branch: master

commit 257b512b3eb078c9874e7ec370c4685f6593fce8
Author: Ashok Singh <email address hidden>
Date: Wed Mar 2 02:35:03 2016 -0800

Update Aging time for TCP flow-stats-collector

When aging time is changed via introspect it was updated only for
default flow-stats-collector. We need to update the aging time for
implicitly added TCP flow-stats-collector as well. However this
update should not be done when TCP flow-stats-collector is configured
explicitly via configuration (Protocol based aging config)

Closes-Bug: #1551201
(cherry picked from commit 54becf8482dfcdcc3a2180f4cf4ff348c815bfbc)

Change-Id: I91fa0dbce6918ff12ab3c1c436e6f2dec7d0f0f7

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.