grub-pc 2.04-1ubuntu29 fails to install on groovy 20.10 due to pkg deps conflict
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-kernel-tests |
Fix Released
|
High
|
Unassigned | ||
| grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Series: Groovy
Arch: AMD64
When attempting to deploy Groovy AMD64 images via MAAS, the deployment is failing due to curtin attempting to install grub-pc (2.04-1ubuntu29 ) which fails to install due to a depends issue noted below.
This has essentially broken all maas deployments at least on Groovy AMD64 at this time.
Setting up linux-generic (5.8.0.16.18) ...
Setting up grub-pc (2.04-1ubuntu29) ...
Creating config file /etc/default/grub with new version
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of grub-gfxpayload
Package grub-pc is not configured yet.
dpkg: error processing package grub-gfxpayload
dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.18-1ubuntu1) ...
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for libc-bin (2.31-0ubuntu10) ...
Processing triggers for systemd (246.2-1ubuntu1) ...
Running in chroot, ignoring command 'daemon-reload'
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for linux-image-
Errors were encountered while processing:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.050
Running command ['umount', '/tmp/tmpu39p2a
Running command ['umount', '/tmp/tmpu39p2a
Running command ['umount', '/tmp/tmpu39p2a
Running command ['umount', '/tmp/tmpu39p2a
finish: cmd-install/
finish: cmd-install/
Traceback (most recent call last):
File "/curtin/
ret = args.func(args)
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
return install_
File "/curtin/
return inchroot.subp(cmd, env=env)
File "/curtin/
return subp(*args, **kwargs)
File "/curtin/
return _subp(*args, **kwargs)
File "/curtin/
raise ProcessExecutio
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpu39p2a
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpu39p2a
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
Stderr: ''

So after looking around a bit it would appear there is another version of grub2 that has been uploaded to the builders. (Version 2.04-1ubuntu30)
https:/ /launchpad. net/ubuntu/ +source/ grub2/2. 04-1ubuntu30
Appears to have 2 fixes:
* postinst.in: do not attempt to call grub-install upon fresh install of
grub-pc because it it a job of installers to do that after fresh
install.
* grub-multi-install: fix non-interactive failures for grub-efi like it
was fixed in postinst for grub-pc.
Not sure if this problem would be addressed in here, however the amd64 deb has failed to build and I have notified the appropriate xnoxx