When replacing a rule, kernel nowadays seems to report rule add event
before rule delete one. Since both events belong to the same
transaction, this is harmless per definition and merely needs adjustment
in expected output.
Signed-off-by: Phil Sutter <p...@nwl.cc>
---
tests/monitor/testcases/simple.t | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/monitor/testcases/simple.t b/tests/monitor/testcases/simple.t
index 78d8f8b04bd36..78fd6616eb074 100644
--- a/tests/monitor/testcases/simple.t
+++ b/tests/monitor/testcases/simple.t
@@ -18,10 +18,10 @@ O add rule ip t c counter packets 0 bytes 0 accept
J {"add": {"rule": {"family": "ip", "table": "t", "chain": "c", "handle": 0,
"expr": [{"counter": {"packets": 0, "bytes": 0}}, {"accept": null}]}}}
I replace rule ip t c handle 2 accept comment "foo bar"
-O delete rule ip t c handle 2
O add rule ip t c accept comment "foo bar"
-J {"delete": {"rule": {"family": "ip", "table": "t", "chain": "c", "handle":
0, "expr": [{"accept": null}]}}}
+O delete rule ip t c handle 2
J {"add": {"rule": {"family": "ip", "table": "t", "chain": "c", "handle": 0,
"comment": "foo bar", "expr": [{"accept": null}]}}}
+J {"delete": {"rule": {"family": "ip", "table": "t", "chain": "c", "handle":
0, "expr": [{"accept": null}]}}}
I add counter ip t cnt
O add counter ip t cnt { packets 0 bytes 0 }
--
2.21.0
