| 2021-07-20 07:35:29 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2021-07-20 07:35:38 |
Christian Ehrhardt |
tags |
|
update-excuse |
|
| 2021-07-20 07:35:47 |
Christian Ehrhardt |
bug task added |
|
nftables (Ubuntu) |
|
| 2021-07-20 07:38:00 |
Christian Ehrhardt |
description |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
Furthermore it is yet unclear if this is locally reproducible. |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
Furthermore it is yet unclear if this is locally reproducible. |
|
| 2021-07-20 07:42:24 |
Christian Ehrhardt |
description |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
Furthermore it is yet unclear if this is locally reproducible. |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
TODO:
- Furthermore it is yet unclear if this is locally reproducible.
- this is old enough someone else might have debugged this but missed to file bugs? |
|
| 2021-07-20 07:45:57 |
Christian Ehrhardt |
description |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
TODO:
- Furthermore it is yet unclear if this is locally reproducible.
- this is old enough someone else might have debugged this but missed to file bugs? |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
With the right keywords I've found closed bugs in firewalld pointing to a nftables fix:
- https://github.com/firewalld/firewalld/issues/752 (thanks locutus for filing)
- https://marc.info/?l=netfilter-devel&m=161221629204555&w=2 <- supposed to be the fix
TODO:
- Furthermore it is yet unclear if this is locally reproducible. |
|
| 2021-07-20 07:47:11 |
Christian Ehrhardt |
description |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
With the right keywords I've found closed bugs in firewalld pointing to a nftables fix:
- https://github.com/firewalld/firewalld/issues/752 (thanks locutus for filing)
- https://marc.info/?l=netfilter-devel&m=161221629204555&w=2 <- supposed to be the fix
TODO:
- Furthermore it is yet unclear if this is locally reproducible. |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
With the right keywords I've found closed bugs in firewalld pointing to a nftables fix:
- https://github.com/firewalld/firewalld/issues/752 (thanks locutus for filing)
- https://marc.info/?l=netfilter-devel&m=161221629204555&w=2 <- supposed to be the fix
The issue is locally reproducible in e.g. autopkgtest VM and thereby
fixes can be tested the same way. |
|
| 2021-07-20 07:49:38 |
Christian Ehrhardt |
description |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
With the right keywords I've found closed bugs in firewalld pointing to a nftables fix:
- https://github.com/firewalld/firewalld/issues/752 (thanks locutus for filing)
- https://marc.info/?l=netfilter-devel&m=161221629204555&w=2 <- supposed to be the fix
The issue is locally reproducible in e.g. autopkgtest VM and thereby
fixes can be tested the same way. |
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/firewalld/20210510_135128_36f9c@/log.gz
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/s390x
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/f/firewalld/20210510_131115_faeb7@/log.gz
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
https://github.com/firewalld/firewalld/issues?q=is%3Aissue+is%3Aopen
does not list those cases, but there is a new v9.4.0 that we might try.
In Debian this isn't showing up
https://ci.debian.net/packages/f/firewalld/
Because they are all Skipped for not having machine level isolation
https://ci.debian.net/data/autopkgtest/testing/amd64/f/firewalld/13738304/log.gz
In detail it seems there re two cases of expected-output-mismatch
in #97:
-icmp type destination-unreachable icmp code host-prohibited reject with icmpx type admin-prohibited
+icmp code host-prohibited reject with icmpx type admin-prohibited
in #124:
-icmpv6 type parameter-problem icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
+icmpv6 code no-route mark set mark & 0x00000086 ^ 0x00000086
Those look like they might have the same root cause.
It seems that this is present for a while, this is nftables nftables/0.9.8-1 in Hirsute half a year ago.
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20210118_230221_66bea@/log.gz
before nftables 0.9.8 it worked on 0.9.7-1:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/f/firewalld/20201101_064747_2b123@/log.gz
With the right keywords I've found closed bugs in firewalld pointing to a nftables fix:
- https://github.com/firewalld/firewalld/issues/752 (thanks Costamagna/Michael for filing)
- https://marc.info/?l=netfilter-devel&m=161221629204555&w=2 <- supposed to be the fix
The issue is locally reproducible in e.g. autopkgtest VM and thereby
fixes can be tested the same way. |
|
| 2021-07-20 07:53:03 |
Christian Ehrhardt |
nftables (Ubuntu): status |
New |
Triaged |
|
| 2021-07-20 07:53:08 |
Christian Ehrhardt |
firewalld (Ubuntu): status |
New |
Confirmed |
|
| 2021-07-20 07:53:12 |
Christian Ehrhardt |
firewalld (Ubuntu): status |
Confirmed |
Invalid |
|
| 2021-07-20 12:24:21 |
Christian Ehrhardt |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991309 |
|
| 2021-07-20 12:24:21 |
Christian Ehrhardt |
attachment added |
|
fix-lp-1936902-impish.debdiff https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1936902/+attachment/5512234/+files/fix-lp-1936902-impish.debdiff |
|
| 2021-07-20 12:29:40 |
Ubuntu Foundations Team Bug Bot |
tags |
update-excuse |
patch update-excuse |
|
| 2021-07-20 12:39:24 |
Christian Ehrhardt |
bug task added |
|
nftables (Debian) |
|
| 2021-07-20 13:53:30 |
Bug Watch Updater |
nftables (Debian): status |
Unknown |
Fix Committed |
|
| 2021-07-20 23:09:18 |
Launchpad Janitor |
nftables (Ubuntu): status |
Triaged |
Fix Released |
|
| 2021-08-20 15:58:22 |
Bug Watch Updater |
nftables (Debian): status |
Fix Committed |
Fix Released |
|
