noironetworks / opflex / 1805 / 1
79%
master: 68%

LAST BUILD BRANCH: drop-log-redirect-args
DEFAULT BRANCH: master
Ran
Files 270
Run time 11s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 78.944%. First build
TEST_SUITE=travis-build.sh

push

travis-ci-com

Gautam Venkataramanan 
Fix stale entries seen after deletion of service during make check tests (#330)

Issue was happening once every few runs. But then it became unreproducible due to the way threads were scheduled. Tried 25+ times with the fix and things look good.

Description:
- SNAT/DNAT flows will be programmed initially from higher prio Agent thread.
- Low prio Svc Stats thread today programs the flows with stats cookies
later on so that snat/dnat flows become eventually consistent to correlate stats.
- In case svc gets deleted, then agent io thread will delete svc flows immediately.
Since svc stats thread is low priority, it could be in the process of updating
SNAT/DNAT flows after agent thread deleted SNAT/DNAT flows. This can lead to
stale snat/dnat flow entries for that svc.
- To avoid these stale entries, call programServiceSnatDnatFlows() for the deleted
svc so that the stale entries (if any) can be cleared for this service. If there
are no stale entries (already deleted), then the below call is a NO-OP.
- Also, when a svc is deleted, prior to the fix we were looping over list of svcs
to update snat/dnat flows. This loop is needed only for EP updates. For svc updates,
we just need to call programServiceSnatDnatFlows() only once for that svc.

Signed-off-by: Gautam Venkataramanan <gautam.chennai@gmail.com>
(cherry picked from commit 2908590e1)

22300 of 28248 relevant lines covered (78.94%)

3615.04 hits per line

Source Files on job 1805.1 (TEST_SUITE=travis-build.sh)