subiquity

  1. Bug #1996896
  2. Activity log

Activity log for bug #1996896

Date Who What changed Old value New value Message
2022-11-17 13:31:58 Frank Heimes bug added bug
2022-11-17 13:31:58 Frank Heimes attachment added crash_and_logs.tgz https://bugs.launchpad.net/bugs/1996896/+attachment/5631188/+files/crash_and_logs.tgz
2022-11-17 13:32:14 Frank Heimes bug task added ubuntu-z-systems
2022-11-17 13:32:30 Frank Heimes ubuntu-z-systems: importance Undecided High
2022-11-17 13:33:50 Frank Heimes summary installation crashes if proxy server is specified in subiquity Installation crashes if proxy server is specified in subiquity
2022-11-17 13:34:29 Frank Heimes description Usually I do installation without using a proxy, since that is not needed in the environment that I use. But trying to recreate a certain situation I specified a proxy in subiquity (not in the early basic network setup that is done at the console), subiquity crashed on the next screen. I tried 3 different settings and the crash occurred with all of them: 1) http://squid.internal:3128 2) http://squid.internal:3128/ 3) http://<IP address>:3128/ Then I did an exact same installation on the same system, just w/o specifying a proxy and the installation was successful. This happened for me on an s390x LPAR, but I don't think it's really related to s390x per-se (maybe related to the network environment the s390x is in.) I've attached the logs and crash file of all 3 cases, even if I'm sure that it's always the same root cause. 2022-11-17 12:28:30,321 DEBUG root:37 start: subiquity/Install/install/configure_apt/cmd-in-target: curtin command in-target 2022-11-17 12:28:34,659 ERROR root:37 finish: subiquity/Install/install/configure_apt: FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.2206', '--property', 'PrivateMounts=yes', '--setenv', 'PATH=/snap/subiquity/4005/bin:/snap/subiquity/4005/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/4005/bin:/snap/subiquity/4005/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/4005/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/4005/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/4005', '--', '/snap/subiquity/4005/usr/bin/python3.8', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.2206.2"}}', 'in-target', '-t', '/tmp/tmpnsi0z5q9/mount', '--', 'apt-get', 'update']' returned non-zero exit status 100. 2022-11-17 12:28:34,660 DEBUG subiquity.common.errorreport:384 generating crash report 2022-11-17 12:28:34,662 INFO subiquity.common.errorreport:406 saving crash report 'install failed crashed with CalledProcessError' to /var/crash/1668688114.660152674.install_fail.crash 2022-11-17 12:28:34,662 ERROR root:37 finish: subiquity/Install/install: FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.2206', '--property', 'PrivateMounts=yes', '--setenv', 'PATH=/snap/subiquity/4005/bin:/snap/subiquity/4005/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/4005/bin:/snap/subiquity/4005/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/4005/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/4005/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/4005', '--', '/snap/subiquity/4005/usr/bin/python3.8', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.2206.2"}}', 'in-target', '-t', '/tmp/tmpnsi0z5q9/mount', '--', 'apt-get', 'update']' returned non-zero exit status 100. 2022-11-17 12:28:34,662 INFO root:37 start: subiquity/ErrorReporter/1668688114.660152674.install_fail/add_info: InstallerServerLogInfo: 2022-11-17 12:27:03,110 INFO subiquity:152 Starting Subiquity server revision 4005 2022-11-17 12:27:03,110 INFO subiquity:153 Arguments passed: ['/snap/subiquity/4005/lib/python3.8/site-packages/subiquity/cmd/server.py'] 2022-11-17 12:27:03,232 INFO aiohttp.access:233 [17/Nov/2022:12:27:03 +0000] "GET /meta/status?cur=null HTTP/1.1" 200 419 "-" "Python/3.8 aiohttp/3.6.2" 2022-11-17 12:27:03,974 INFO aiohttp.access:233 [17/Nov/2022:12:27:03 +0000] "GET /meta/status?cur=null HTTP/1.1" 200 419 "-" "Python/3.8 aiohttp/3.6.2" Usually I do installation without using a proxy, since that is not needed in the environment that I use. But trying to recreate a certain situation I specified a proxy in subiquity (not in the early basic network setup that is done at the console), subiquity crashed on the next screen. I tried 3 different settings and the crash occurred with all of them: 1) http://squid.internal:3128 2) http://squid.internal:3128/ 3) http://<IP address>:3128/ Then I did an exact same installation on the same system, just w/o specifying a proxy and the installation was successful. This happened for me on an s390x LPAR, but I don't think it's really related to s390x per-se (maybe related to the network environment the s390x is in.) I've attached the logs and crash file of all 3 cases, even if I'm sure that it's always the same root cause.  2022-11-17 12:28:30,321 DEBUG root:37 start: subiquity/Install/install/configure_apt/cmd-in-target: curtin command in-target  2022-11-17 12:28:34,659 ERROR root:37 finish: subiquity/Install/install/configure_apt: FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.2206', '--property', 'PrivateMounts=yes', '--setenv', 'PATH=/snap/subiquity/4005/bin:/snap/subiquity/4005/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/4005/bin:/snap/subiquity/4005/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/4005/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/4005/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/4005', '--', '/snap/subiquity/4005/usr/bin/python3.8', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.2206.2"}}', 'in-target', '-t', '/tmp/tmpnsi0z5q9/mount', '--', 'apt-get', 'update']' returned non-zero exit status 100.  2022-11-17 12:28:34,660 DEBUG subiquity.common.errorreport:384 generating crash report  2022-11-17 12:28:34,662 INFO subiquity.common.errorreport:406 saving crash report 'install failed crashed with CalledProcessError' to /var/crash/1668688114.660152674.install_fail.crash  2022-11-17 12:28:34,662 ERROR root:37 finish: subiquity/Install/install: FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.2206', '--property', 'PrivateMounts=yes', '--setenv', 'PATH=/snap/subiquity/4005/bin:/snap/subiquity/4005/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/4005/bin:/snap/subiquity/4005/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/4005/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/4005/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/4005', '--', '/snap/subiquity/4005/usr/bin/python3.8', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.2206.2"}}', 'in-target', '-t', '/tmp/tmpnsi0z5q9/mount', '--', 'apt-get', 'update']' returned non-zero exit status 100.  2022-11-17 12:28:34,662 INFO root:37 start: subiquity/ErrorReporter/1668688114.660152674.install_fail/add_info: InstallerServerLogInfo:  2022-11-17 12:27:03,110 INFO subiquity:152 Starting Subiquity server revision 4005  2022-11-17 12:27:03,110 INFO subiquity:153 Arguments passed: ['/snap/subiquity/4005/lib/python3.8/site-packages/subiquity/cmd/server.py']  2022-11-17 12:27:03,232 INFO aiohttp.access:233 [17/Nov/2022:12:27:03 +0000] "GET /meta/status?cur=null HTTP/1.1" 200 419 "-" "Python/3.8 aiohttp/3.6.2"  2022-11-17 12:27:03,974 INFO aiohttp.access:233 [17/Nov/2022:12:27:03 +0000] "GET /meta/status?cur=null HTTP/1.1" 200 419 "-" "Python/3.8 aiohttp/3.6.2" (Btw. I've tried this on kinetic only so far ...)
2024-03-18 12:27:20 Frank Heimes tags installer s390x installation s390x