A bug in proxmox-ve-config caused the key to be defaulted to on, if it didn't exist in the configuration. Add this scenario to the integration tests, so we can potentially catch problems with the missing firewall key via the integration tests.
Signed-off-by: Stefan Hanreich <s.hanre...@proxmox.com> --- proxmox-firewall/tests/input/100.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/proxmox-firewall/tests/input/100.conf b/proxmox-firewall/tests/input/100.conf index 495f899..cf9af7f 100644 --- a/proxmox-firewall/tests/input/100.conf +++ b/proxmox-firewall/tests/input/100.conf @@ -4,6 +4,7 @@ features: nesting=1 hostname: host1 memory: 512 net1: name=eth0,bridge=simple1,firewall=1,hwaddr=BC:24:11:4D:B0:FF,ip=dhcp,ip6=fd80::1234/64,type=veth +net2: name=eth0,bridge=simple1,hwaddr=BC:24:11:4D:B0:FF,ip=dhcp,ip6=fd80::1234/64,type=veth ostype: debian rootfs: local-lvm:vm-90001-disk-0,size=2G swap: 512 -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
