[Bug 2089320] Re: Secure boot variables full, unable to boot

[Rod Smith]

I'm attaching complete boot logs (IPMI SoL output) from three boot
attempts. The failed-sb-enabled.txt and failed-sb-disabled.txt logs are
from attempts that failed with Secure Boot enabled and disabled,
respectively, in the firmware settings. (Both are from attempts to
deploy Ubuntu 22.04.) After using the firmware setup utility to clear
the db and dbx variables, and disabling Secure Boot, I was able to
deploy Ubuntu 22.04; the successful-sb-disabled.txt file shows the IPMI
SoL output from that deployment.

Currently, the system in question (I was using the same one that Pedro
used), is deployable with both Ubuntu 22.04 and 24.04, with Secure Boot
disabled. I have no tried re-enabling Secure Boot since getting it
working.

** Attachment added: "IPMI SoL output of three boot attempts"
   https://bugs.launchpad.net/ubuntu/+source/shim/+bug/2089320/+attachment/5856937/+files/boot-logs.zip

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/2089320

Title:
  Secure boot variables full, unable to boot

Status in shim package in Ubuntu:
  New

Bug description:
  Deploying 22.04 fills up the secure boot variable Forbidden
  Signatures. The system is still able to boot, but there are warnings
  when booting. However, deploying with 24.04 seems to fill the secure
  boot variable so much that the Ubuntu install is unable to start.

  This behavior was noticed when deploying through MAAS to a Supermicro
  - SYS-6028U-TR4+
  (https://www.supermicro.com/products/system/2u/6028/SYS-6028U-TR4_.cfm?parts=SHOW)
  system.

  
  This is the output I was able to capture from the terminal:

  ```
  Could not create MokListTrustedRT: Volume full
  Something has gone seriously wrong: import_mok_state() failed: Volume full
  ```

  The error messages were similar to the ones found in this upstream
  issue: https://github.com/rhboot/shim/issues/654.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/2089320/+subscriptions