Comment 1 for bug 1708030

The possible problem here is zone_id created by netlink-lib during functional tests duplicated with zone_id created by something else. In this test case, netlink-lib lists all conntrack entries in OS with zone_id is '10', but some other entries with zone '10' already existed hence the test didn't work properly.

Problem is in the test case, netlink-lib doesn't create these two conntrack entries
(4, 'tcp', 40364, 12345, '192.168.0.1', '192.168.0.2', 10), (4, 'tcp', 59330, 12346, '192.168.0.1', '192.168.0.2', 10) so I'm in doubt that these conntrack entries somehow already existed before tests running.