mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-25 01:34:11 +03:00
e66451f685
All the unit tests that use iptables/ip6tables/ebtables have been written to omit the locking/exclusive use primitive on the generated commandlines. Even though none of the tests actually execute those commands (and so it doesn't matter for purposes of the test whether or not the commands support these options), it still made sense when some systems had these locking options and some didn't. We are now at a point where every supported Linux distro has supported the locking options on these commands for quite a long time, and are going to make their use non-optional. As a first step, this patch uses the virFirewallSetLockOverride() function, which is called at the beginning of all firewall-related tests, to set all the bools controlling whether or not the locking options are used to true. This means that all the test cases must be updated to include the proper locking option in their commandlines. The change to make actual execs of the commands unconditionally use the locking option will be in an upcoming patch - this one affects only the unit tests. Signed-off-by: Laine Stump <laine@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com> |
||
|---|---|---|
| .. | ||
| base.args | ||
| nat-default-linux.args | ||
| nat-default.xml | ||
| nat-ipv6-linux.args | ||
| nat-ipv6-masquerade-linux.args | ||
| nat-ipv6-masquerade.xml | ||
| nat-ipv6.xml | ||
| nat-many-ips-linux.args | ||
| nat-many-ips.xml | ||
| nat-no-dhcp-linux.args | ||
| nat-no-dhcp.xml | ||
| nat-tftp-linux.args | ||
| nat-tftp.xml | ||
| route-default-linux.args | ||
| route-default.xml | ||