curtin.util.ProcessExecutionError: Unexpected error while running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram', '/target', '/dev/sda']

Bug #1766286 reported by sudodus on 2018-04-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
Undecided
Unassigned

Bug Description

It works in the same computer running in BIOS mode, but failed in UEFI mode

       Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
        finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command curthooks
        Traceback (most recent call last):
          File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 201, in main
            ret = args.func(args)
          File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", line 1103, in curthooks
            setup_grub(cfg, target)
          File "/usr/lib/python3/dist-packages/curtin/commands/curthooks.py", line 407, in setup_grub
            join_stdout_err + args + instdevs, env=env, capture=True)
          File "/usr/lib/python3/dist-packages/curtin/util.py", line 263, in subp
            return _subp(*args, **kwargs)
          File "/usr/lib/python3/dist-packages/curtin/util.py", line 131, in _subp
            cmd=args)
        curtin.util.ProcessExecutionError: Unexpected error while running command.
        Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram', '/target', '/dev/sda']
        Exit code: 1
        Reason: -
        Stdout: carryover command line params:
                curtin uefi: installing grub-efi-amd64 to: /boot/efi
                + echo before grub-install efiboot settings
                before grub-install efiboot settings
                + efibootmgr
                BootCurrent: 0000
                Timeout: 0 seconds
                BootOrder: 2001,2003,2002
                Boot0000* EFI USB Device (JetFlashTranscend 32GB)
                Boot0001* EFI Network 0 for IPv6 (70-54-D2-31-33-2D)
                Boot0002* EFI Network 0 for IPv4 (70-54-D2-31-33-2D)
                Boot2001* EFI USB Device
                Boot2002* EFI DVD/CDROM
                Boot2003* EFI Network
                + dpkg-reconfigure grub-efi-amd64
                Replacing config file /etc/default/grub with new version
                Processing triggers for shim-signed (1.34.4+13-0ubuntu2) ...
                No MOK found.
                dpkg: error processing package shim-signed (--configure):
                 installed shim-signed package post-installation script subprocess returned error exit status 1
                Errors were encountered while processing:
                 shim-signed
                failed to install grub!

        Stderr: ''
        Unexpected error while running command.
        Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram', '/target', '/dev/sda']
        Exit code: 1
        Reason: -

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-server 1.417
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CasperVersion: 1.393
Date: Mon Apr 23 15:31:41 2018
LiveMediaBuild: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

sudodus (nio-wiklund) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1766286

tags: added: iso-testing
Brian Murray (brian-murray) wrote :

The error is really about shim-signed.

affects: ubuntu-meta (Ubuntu) → shim-signed (Ubuntu)
Steve Langasek (vorlon) wrote :

This is a bug in an earlier revision of shim-signed which has now been superseded. The current fixed version of shim is 1.34.7. please retest with a newer image including this version.

Changed in shim-signed (Ubuntu):
status: New → Fix Released
sudodus (nio-wiklund) wrote :

Sorry, it is still failing.

Is the following iso file the correct one to use?

$ md5sum bionic-live-server-amd64.iso
70051f7b2125674f1821e7d7674f1609 bionic-live-server-amd64.iso

$ ls -l bionic-live-server-amd64.iso
-rw------- 1 nio nio 845152256 apr 24 06:57 bionic-live-server-amd64.iso

sudodus (nio-wiklund) wrote :

The install iso does not contain any shim-signed package, and it refers to a previous candidate. Maybe I should wait for the next iso file?
---
$ apt-cache policy shim-signed
shim-signed:
  Installed: (none)
  Candidate: 1.34.6+13-0ubuntu2
  Version table:
     1.34.6+13-0ubuntu2 500
        500 cdrom://Ubuntu-Server 18.04 LTS _Bionic Beaver_ - Release amd64 (20180424.1) bionic/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---

Steve Langasek (vorlon) wrote :

Your following logs show that shim-signed 1.34.7+13-0ubuntu2 was pulled in by curtin.

However, we've also identified that LP: #1766627 affects this version of shim-signed, so that's probably what you were originally experiencing and is definitely what you are seeing now.

A final fix for this bug is in progress; shim-signed 1.34.9 is expected to completely resolve this issue, and will land in the next round of image builds.

sudodus (nio-wiklund) wrote :

The current iso file

$ md5sum bionic-live-server-amd64.iso
88bae744442a9047534b129b3d3d0d33 bionic-live-server-amd64.iso
$ ls -l bionic-live-server-amd64.iso
-rw------- 1 nio nio 845152256 apr 25 04:00 bionic-live-server-amd64.iso

is better. The installer finishes and exclaims "Installation complete!"

After reboot I have a server booted in UEFI mode.

Thanks for squashing this bug :-)

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

Other bug subscribers