Hello Andreas, or anyone else affected,

Accepted iptables into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/iptables/1.8.4-3ubuntu2.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: iptables (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2019023

Title:
  Fix shell test suite

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  The shell test suite (iptables/tests/shell/run-tests.sh) is currently
  failing on the firewalld tests in focal only:

  W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but 
got 1
  W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: 
expected 0 but got 1

  After some troubleshooting, it turns out this is happening because of
  an unsorted order in the output of iptables-save, which was fixed[1]
  in later releases of iptables. The code was trying to compensate for
  that, but there was a small mistake[2] in a case/esac globbing:

  case "$XT_MULTI" in
  -*/xtables-nft-multi)
  +*xtables-nft-multi)

  The upstream fix includes other similar changes in other tests, but in
  the case of focal, the above is the minimal fix needed.

  Note that this shell test suite is not being run in focal, just in
  later ubuntu releases. But since the fix for #1992454 is adding such a
  test, I decided to fix the shell test run and add it to the existing
  DEP8 tests for focal via this bug, so we have test parity between
  focal and later ubuntu releases.

  1. 
https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef
  2. 
https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6

  [ Test Plan ]
  Verify that the DEP8 tests now include a run-tests.sh test suite, and that it 
passes.

  [ Where problems could occur ]
  If the fix is incorrect, it would affect only the already-failing firewalld 
test. But in addition to fixing that test, we are now also including a full 
test run of all shell tests, something which wasn't being done for focal until 
now. While these tests are passing now, they could fail in a future iptables 
SRU, or turn out to be flaky. They are being run in ubuntu releases after 
focal, though, so that is a good sign.

  [ Other Info ]
  This fix is being included in the same upload as bug #1992454.

  [ Original Description ]

  The shell test suite (iptables/tests/shell/run-tests.sh) is currently
  failing on the firewalld tests:

  W: [FAILED]      ././testcases/firewalld-restore/0001-firewalld_0: expected 0 
but got 1
  W: [FAILED]      ././testcases/firewalld-restore/0002-firewalld-restart_0: 
expected 0 but got 1

  After some troubleshooting, it turns out this is happening because of
  an unsorted order in the output of iptables-save, which was fixed[1]
  in later releases of iptables. The code was trying to compensate for
  that, but there was a small mistake[2] in a case/esac globbing:

  case "$XT_MULTI" in
  -*/xtables-nft-multi)
  +*xtables-nft-multi)

  1. 
https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef
  2. 
https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019023/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to