Public bug reported: An attempt to merge sshuttle prior to jammy FF failed, because of autopkgtest failures.
The delta between Debian and Ubuntu is d/t/* only. A v1.1.0-1ubuntu1 is available here: https://launchpad.net/~fheimes/+archive/ubuntu/sshuttle The failures can be found here: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ddstreet-sponsor/jammy/amd64/s/sshuttle/20220224_214719_d5d00@/log.gz Especially: --------%<----------------%<----------------%<----------------%<-------- remote-trusty: lxc start remote-trusty remote-trusty: Waiting for remote-trusty to finish starting this ssh connection should timeout: running: lxc exec remote-trusty -- ssh -o ConnectionAttempts=2 -v 10.252.0.1 -- cat /proc/sys/kernel/hostname ssh: connect to host 10.252.0.1 port 22: No route to host ssh failed (as expected) running: lxc exec remote-trusty -- sshuttle --python python3 -r 10.254.0.2 10.252.0.0/24 waiting for sshuttle to start....sshuttle failed :-( skipped 'This is an expected failure, ignoring test failure' ERROR ====================================================================== ERROR: setUpClass (__main__.SshuttleTest_xenial) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 544, in setUpClass remote = Remote(f'remote-{cls.release}', cls.release) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 287, in __init__ self._wait_for_networking() File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 319, in _wait_for_networking raise Exception(f'Timed out waiting for remote {self.name} networking') Exception: Timed out waiting for remote remote-xenial networking ====================================================================== FAIL: test_local_to_remote_nopy (__main__.SshuttleTest_trusty) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 661, in test_local_to_remote_nopy self._test_to_remote(self, self.remote, None) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 683, in _test_to_remote self.sshuttle_start(dst, python) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 608, in sshuttle_start self.fail('sshuttle process failed to start') VerboseAssertionError: sshuttle process failed to start Test detail: testbed-trusty sshuttle 1.1.0-1ubuntu1 to remote-trusty ====================================================================== FAIL: test_local_to_remote_py2 (__main__.SshuttleTest_trusty) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 664, in test_local_to_remote_py2 self._test_to_remote(self, self.remote, 'python2') File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 683, in _test_to_remote self.sshuttle_start(dst, python) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 608, in sshuttle_start self.fail('sshuttle process failed to start') VerboseAssertionError: sshuttle process failed to start Test detail: testbed-trusty sshuttle 1.1.0-1ubuntu1 to remote-trusty python2 ====================================================================== FAIL: test_remote_to_reverse_remote_nopy (__main__.SshuttleTest_trusty) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 670, in test_remote_to_reverse_remote_nopy self._test_to_remote(self.remote, self.reverse_remote, None) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 683, in _test_to_remote self.sshuttle_start(dst, python) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 608, in sshuttle_start self.fail('sshuttle process failed to start') VerboseAssertionError: sshuttle process failed to start Test detail: remote-trusty sshuttle 0.54-2 to reverse-remote-jammy ====================================================================== FAIL: test_remote_to_reverse_remote_py2 (__main__.SshuttleTest_trusty) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 673, in test_remote_to_reverse_remote_py2 self._test_to_remote(self.remote, self.reverse_remote, 'python2') File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 683, in _test_to_remote self.sshuttle_start(dst, python) File "/tmp/autopkgtest.IbY0Uu/build.hRt/src/debian/tests/cross-release", line 608, in sshuttle_start self.fail('sshuttle process failed to start') VerboseAssertionError: sshuttle process failed to start Test detail: remote-trusty sshuttle 0.54-2 to reverse-remote-jammy python2 ---------------------------------------------------------------------- Ran 30 tests in 2749.995s FAILED (failures=4, errors=1, skipped=2) --------%<----------------%<----------------%<----------------%<-------- It seems that this is likely due to jammy's move to cgroup2, which now prevents older trusty and xenial containers from starting. Options are: 1) fix trusty and xenial to be able to boot as a container under jammy 2) disable the tests against trusty and xenial (which would be unfortunate, since its idea is to ensure Ubuntu cross-release compatibility of sshuttle) This needs further investigations and discussions, hence opening this FFe. ** Affects: sshuttle (Ubuntu) Importance: Undecided Status: New ** Tags: jammy needs-merge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962286 Title: [FFE] sshuttle merged to 1.1.0-1ubuntu1 fails autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1962286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
