subiquity

18.04 Server - Subiquity installer fails

Bug #1767584 reported by Adam on 2018-04-28

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	curtin	Fix Released	High	Unassigned
	subiquity	Fix Released	Undecided	Unassigned

Bug Description

Installing Ubuntu server 18.04 fails with an error using the subiquity installer.

See original description

Related branches

~raharper/curtin:fix/lp-1767584-efiboot-parse

Merged into curtin:master at revision c8209ef76ff332b1dd004329437a46338105b9ab

Scott Moser (community): Approve on 2018-04-30

Server Team CI bot: Approve (continuous-integration) on 2018-04-30

Revision history for this message

Adam (agustafson15) wrote on 2018-04-28:

subiquity-debug.log Edit (39.8 KiB, text/plain)

description:

updated

Revision history for this message

Adam (agustafson15) wrote on 2018-04-28:

curtin-error-logs.tar Edit (160.0 KiB, application/x-tar)

Revision history for this message

Adam (agustafson15) wrote on 2018-04-28:

syslog Edit (9.6 MiB, text/plain)

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2018-04-30:

Hi, thanks for digging out the curtin error logs!

The failing command is this:

efibootmgr -o 0001,0000,3000,2001,2002,2003

Which fails with

Invalid BootOrder order entry value0001,0000,3000,2001,2002,2003
^
efibootmgr: entry 2003 does not exist

On the basis of which I'm going to add a curtin bug task (I don't know much about this end of things myself). I see this is a "HP ENVY TouchSmart 17t-j100", do you know if this model is known to have problems with its UEFI implementation? I know some HP laptops do.

Revision history for this message

Adam (agustafson15) wrote on 2018-04-30:

I don't know, I haven't had any problems before and I updated to the latest bios without any luck.

Revision history for this message

Ryan Harper (raharper) wrote on 2018-04-30:

I believe this is an issue with curtin's use of efibootmgr. We're calling efibootmgr with -o, --bootorder which the manpage says, each entry must exist:

-o | --bootorder XXXX,YYYY,ZZZZ
Explicitly set BootOrder (hex). Any value from 0 to FFFF is accepted so long as it corresponds to an existing Boot#### variable, and zero padding is not required.

Curtin should adjust the order value and drop any entry reference to a value that's not found in the entry list.

Changed in curtin:
importance:	Undecided → High
status:	New → Confirmed

Ryan Harper (raharper) on 2018-04-30

Changed in curtin:
status:	Confirmed → In Progress

Revision history for this message

Kirk (kjg291) wrote on 2018-04-30:

I have been unable to complete the installation on a HP Envy dv6-7247cl because of the same bug.

Revision history for this message

Scott Moser (smoser) wrote on 2018-05-08:

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=c8209ef7

Changed in curtin:
status:	In Progress → Fix Committed

Revision history for this message

Ryan Harper (raharper) wrote on 2018-06-01: Fixed in curtin version 18.1-17-gae48e86f-0ubuntu1.

This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-0ubuntu1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.