It fails the same way across architectures in:
## ------------------------ ##
## Summary of the failures. ##
## ------------------------ ##
Failed tests:
firewalld 0.9.3 test suite test groups:
NUM: FILE-NAME:LINE TEST-GROUP-NAME
KEYWORDS
97: icmp_block_in_forward_chain.at:1 ICMP block present FORWARD chain
nftables icmp
124: rhbz1855140.at:1 rich rule icmptypes with one family
nftables rich icmp rhbz1855140
The new nftables /launchpad. net/ubuntu/ +source/ nftables/ 0.9.8-3 /autopkgtest. ubuntu. com/packages/ f/firewalld/ impish/ amd64 /autopkgtest. ubuntu. com/results/ autopkgtest- impish/ impish/ amd64/f/ firewalld/ 20210510_ 135128_ 36f9c@/ log.gz /autopkgtest. ubuntu. com/packages/ f/firewalld/ impish/ s390x /autopkgtest. ubuntu. com/results/ autopkgtest- impish/ impish/ s390x/f/ firewalld/ 20210510_ 131115_ faeb7@/ log.gz
https:/
is stuck in proposed since it fails autopkgtest of firewalld
https:/
https:/
https:/
https:/
It fails the same way across architectures in: ------- ------- --- ## ------- ------- --- ##
## -------
## Summary of the failures. ##
## -------
Failed tests:
firewalld 0.9.3 test suite test groups:
NUM: FILE-NAME:LINE TEST-GROUP-NAME
KEYWORDS
97: icmp_block_ in_forward_ chain.at: 1 ICMP block present FORWARD chain
nftables icmp
124: rhbz1855140.at:1 rich rule icmptypes with one family
nftables rich icmp rhbz1855140
The upstream issue tracker /github. com/firewalld/ firewalld/ issues? q=is%3Aissue+ is%3Aopen
https:/
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up /ci.debian. net/packages/ f/firewalld/ /ci.debian. net/data/ autopkgtest/ testing/ amd64/f/ firewalld/ 13738304/ log.gz
https:/
Because they are all Skipped for not having machine level isolation
https:/
Furthermore it is yet unclear if this is locally reproducible.