Noble Server daily does not recognise SecureBoot

Bug #2046107 reported by Mike Ferreira
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
Expired
Undecided
Unassigned

Bug Description

Noble Server Daily: 20231210

Similar to Bug Report https://bugs.launchpad.net/subiquity/+bug/2046036 in that it does no trecognise that SecureBoot is enabled, does not recognise that it needs to enroll the mokutil key, so does not trigger that process in the installer, and on next boot does not prompt to enroll the key, but...

It does reboot and fails right into the cloudinit process, locked up at the point.

On reboot, if you disable SecureBoot, it will boot.

This will fail CIS and STIG Compliance... So will present a security issue.

Tags: iso-testing
Revision history for this message
Mike Ferreira (mafoelffen) wrote :

Since it is a server with no GUI, here is the uploaded bug / system information.

Revision history for this message
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/2046107

tags: added: iso-testing
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Testing Ubuntu Server Noble daily ISO dated 13-01-2024 - unable to reproduce this bug .

Test machine - AWOW NY41 – Int.Cel. J4125, 8GB, 128GB SSD,Intel UHD Graphics 600Dual Band WiFi,Ethernet,BT5.1
UEFI+secure boot enabled

Revision history for this message
Dan Bungert (dbungert) wrote (last edit ):

Thanks for the reports.

I have merged the 3 bugs into this one as I expect that they have all the same root cause. If we decide later that was incorrect they can be split.

MOK enrollment is unrelated to this problem, and need not be tracked here (we're aware)

A tarball of /var/log/installer will be necessary to gather the required info to proceed.

Changed in subiquity:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for subiquity because there has been no activity for 60 days.]

Changed in subiquity:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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