Upgrade tests with uefi and uefi+secureboot

Bug #1557128 reported by Dave Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Upgrade Testing
In Progress
High
Max Brustkern

Bug Description

STEPS:
1. locally setup a kvm instance for uefi and secureboot
2. Set the cpu to -cpu host
3. during the install of 14.04 clcik on 3rd party drivers
4. Complete the install and trigger the upgrade

EXPECTED:
During the upgrade you will be asked for permission to disable secureboot using mokutil to disable secureboot for this instance at a desktop level (i.e. if you look at the bios it still reads that secureboot is enabled.)

The same is true of installs.

Info on setup for this can be found at https://wiki.canonical.com/UES/QA/Daves_brain_dump_page#KVM_Setups and https://wiki.ubuntu.com/SecurityTeam/SecureBoot

To re-enable secureboot:
Run:
sudo mokutil --enable-validation this will ask for a password again re-enter it in the bios run and then enable secureboot once more.

Revision history for this message
Max Brustkern (nuclearbob) wrote :

I'm going to work on 4 tests:
0. We can upgrade a UEFI-enabled system and it still boots using UEFI (already working)
1. We can upgrade a secureboot-enabled system and it still boots using secureboot
2. If we install 3rd party drivers and upgrade, debconf brings up a dialog to ask us about things
3. If we install 3rd party drivers and upgrade and set the necessary things to prevent that debconf dialog, the upgrade works and we can still boot.

Changed in auto-upgrade-testing:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Max Brustkern (nuclearbob)
Revision history for this message
Max Brustkern (nuclearbob) wrote :

cyphermox would like to make sure a new install works, will add to tests.

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

Other bug subscribers

Remote bug watches

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