What is it that really breaks it - the late message unable to find kernel in /tmp/autopkgtest.EBaDMb/build.J66/src/debian/tests/plucky.d/disk.img - the obvious apt changed message earlier sed: can't read /etc/apt/sources.list: No such file or directory
There is again too much code meant to be generic, no more fitting the needs of just the test. And then on the other hand it does: - not understand deb822 format apt sources - not know that installing from proposed is not default prio anymore - able to find kernel/initrd in UEFI enabled images ... In an ideal world it would need a full overhaul or rewrite. it isn't bad, but good intend that aged badly. For now I'm just removing unused elements as I see them and fixing up the few that are left not working. With all that done (I'll push my progress again to the branch https://code.launchpad.net/~paelzer/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/lp2095584-strip-fix-testlib ) I'm over all the script issues, python incompatibilities and more ... The guest starts off the open-iscsi based disk as far as I can see in my tests. ... [ 460.256885] sh[806]: Completed socket interaction for boot stage network [ OK ] Finished cloud-init-network.service - Cloud-init: Network Stage. [ OK ] Reached target cloud-config.target - Cloud-config availability. [ OK ] Reached target network-online.target - Network is Online. [ OK ] Listening on cloud-init-hotplugd.s…t - cloud-init hotplug hook socket. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [ OK ] Started iscsid.service - iSCSI initiator daemon (iscsid). Starting open-iscsi.service - Login to default iSCSI targets... [ OK ] Finished open-iscsi.service - Login to default iSCSI targets. [ OK ] Reached target remote-fs-pre.targe…reparation for Remote File Systems. [ OK ] Reached target remote-fs.target - Remote File Systems. Starting blk-availability.service - Availability of block devices... [ OK ] Finished blk-availability.service - Availability of block devices. But then it hangs there ... So it seems the next aspect I have to check is what it does with this after starting the guest. What is it waiting on and how is it meant to conclude. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2095584 Title: open-iscsi: ubuntu-only test needs update for Python 3.13 Status in open-iscsi package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: open-iscsi fails its autopkgtest [1] when triggered by python3-defaults/3.13.1-1~exp2 (i.e. with python3.13 as the default Python interpreter). 348s autopkgtest [10:06:35]: test testsuite: [----------------------- 349s /tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py:151: SyntaxWarning: invalid escape sequence '\s' 349s if re.search("^\s*%s\s*=" % (field), line): 349s /tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py:170: SyntaxWarning: invalid escape sequence '\s' 349s if re.search("^\s*%s\s*=" % (field), line): 349s /tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py:345: SyntaxWarning: invalid escape sequence '\(' 349s re.match('^\(' + exe + '\)', tmp[0]): 349s /tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py:345: SyntaxWarning: invalid escape sequence '\)' 349s re.match('^\(' + exe + '\)', tmp[0]): 349s /tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py:734: SyntaxWarning: invalid escape sequence '\(' 349s if re.search('%s \(' % path, line): 349s Traceback (most recent call last): 349s File "/tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/test-open-iscsi.py", line 50, in <module> 349s import testlib 349s File "/tmp/autopkgtest.j5qteT/build.Boe/src/debian/tests/testlib.py", line 23, in <module> 349s import crypt 349s ModuleNotFoundError: No module named 'crypt' 349s autopkgtest [10:06:36]: test testsuite: -----------------------] 350s autopkgtest [10:06:37]: test testsuite: - - - - - - - - - - results - - - - - - - - - - 350s testsuite FAIL non-zero exit status 1 This is not considered a regression due to python3-defaults because open-iscsi also fails its autopkgtest when triggered by migration-reference/0, and has been doing so for a long time (at least since April 2024 in Noble). [1] https://autopkgtest.ubuntu.com/packages/open-iscsi/plucky/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/2095584/+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
