Subiquity crashes installing grub-pc with noble daily build

Bug #2060680 reported by Guillaume
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

Creating a master under QEMU for noble, subiquity crashes when installing grub-pc.

2 things to note :
- our setup works well with u22
- we can create our master using QEMU or VMWare, and subiquity only crashes when using QEMU, everything is fine if we use a VMWare VM

 2024-04-09 11:59:30,346 DEBUG root:30 start: subiquity/Install/install/curtin_install/run_curtin_step/cmd-install/stage-curthooks/builtin/cmd-curthooks/: Installing packages on target system: ['grub-pc']
 2024-04-09 11:59:51,970 ERROR root:30 finish: subiquity/Install/install/curtin_install/run_curtin_step: FAIL:
 2024-04-09 11:59:52,066 ERROR root:30 finish: subiquity/Install/install/curtin_install: FAIL:
 2024-04-09 11:59:52,069 DEBUG subiquity.common.errorreport:398 generating crash report
 2024-04-09 11:59:52,281 INFO subiquity.common.errorreport:424 saving crash report 'curthooks crashed with CurtinInstallError' to /var/crash/1712663992.071365356.install_fail.crash
 2024-04-09 11:59:52,282 ERROR root:30 finish: subiquity/Install/install: FAIL:
 2024-04-09 11:59:52,282 INFO root:30 start: subiquity/ErrorReporter/1712663992.071365356.install_fail/add_info:
 2024-04-09 11:59:52,287 ERROR subiquity.server.server:426 top level error
 Traceback (most recent call last):
   File "/snap/subiquity/5645/lib/python3.10/site-packages/subiquity/server/controllers/install.py", line 246, in run_curtin_step
     await run_curtin_command(
   File "/snap/subiquity/5645/lib/python3.10/site-packages/subiquity/server/curtin.py", line 230, in run_curtin_command
     return await cmd.wait()
   File "/snap/subiquity/5645/lib/python3.10/site-packages/subiquity/server/curtin.py", line 125, in wait
     result = await self.runner.wait(self.proc)
   File "/snap/subiquity/5645/lib/python3.10/site-packages/subiquity/server/runner.py", line 94, in wait
     raise subprocess.CalledProcessError(
 subprocess.CalledProcessError: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.1806', '--setenv', 'PATH=/snap/subiquity/5645/bin:/snap/subiquity/5645/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/5645/bin:/snap/subiquity/5645/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/5645/lib/python3.10/site-packages', '--setenv', 'PYTHON=/snap/subiquity/5645/usr/bin/python3.10', '--setenv', 'SNAP=/snap/subiquity/5645', '--', '/snap/subiquity/5645/usr/bin/python3.10', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.1806.9"}}', '-c', '/var/log/installer/curtin-install/subiquity-curthooks.conf', 'install', '--set', 'json:stages=["curthooks"]']' returned non-zero exit status 1.

Tags: noble
Revision history for this message
Guillaume (e1msih) wrote :
Revision history for this message
Guillaume (e1msih) wrote :
Revision history for this message
Guillaume (e1msih) wrote :
Revision history for this message
Guillaume (e1msih) wrote :
Revision history for this message
Olivier Gayot (ogayot) wrote :

Hello and thank you for your bug report,

Could you please attach the curtin-install.log file that should be available in /var/log/installer?

Thank you,
Olivier

Revision history for this message
Guillaume (e1msih) wrote :

Here's the curtin-install.log you requested, thanks for taking a look at this.

Revision history for this message
Olivier Gayot (ogayot) wrote :

Hello, it looks like the curtin process (or the apt-get process?) got killed.

That could mean that your VM did not have enough memory. How much memory did your QEMU VM have?

Olivier

Revision history for this message
Guillaume (e1msih) wrote :

1 Gb and it seems not enough for noble, altough it's enough for jammy.
I'll try with 2 and 3 Gb to see if it's enough, thanks.

Revision history for this message
Guillaume (e1msih) wrote :

2 Gb of ram isn't enough, 3 Gb ram is okay.
It seems a lot for a text installation, but it's not an isolated case, as RHEL 8 & 9 have the same issue, in my case (U22 / EL 7 and inferiors build well with only 1 Gb).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.