My bug #1766637, regarding recent MAAS deployments of Bionic, has been marked a duplicate of this one. The MAAS logs in that bug seem to indicate that there's a problem accessing /sys/firmware/efi:
Setting up shim (13-0ubuntu2) ... Setting up libefivar1:amd64 (34-1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up sbsigntool (0.6-3.2ubuntu2) ... Setting up libefiboot1:amd64 (34-1) ... Processing triggers for man-db (2.8.3-2) ... Setting up mokutil (0.3.0-0ubuntu5) ... Setting up secureboot-db (1.1) ... Can't access efivars filesystem at /sys/firmware/efi/efivars, aborting For me, the problem is recent -- deployments done a week ago succeeded fine, but today they're failing. (I've done no deployments in the past few days, so I'm not sure exactly when the problem began.) ** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766338 Title: package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1766338/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
