Cubic

Cubic generated image fails on Subiquity Autoinstall

Asked by Alexander Turner

Pulling my hair out with this one and thought I'd try here.

I'm building a custom Ubuntu 20.04 image which I'm auto installing via PXE boot. When I use the source .iso I have no issues with install - however with an _unmodified_ Cubic built image, the install fails on the Subiquity/Curtin install tasks at cmd-curthooks. Any idea how the Cubic image could differ from the original image?

https://imgur.com/wZVJ2Bf

Question information

Language:
English Edit question
Status:
Solved
For:
Cubic Edit question
Assignee:
No assignee Edit question
Solved by:
Alexander Turner
Solved:
Last query:
Last reply:
Revision history for this message
Cubic PPA (cubic-wizard) said : 		#1

I don't know if this is related?...

https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1875560

Revision history for this message
Cubic PPA (cubic-wizard) said : 		#2

In terms of differences...
Cubic adds "boot/casper" to the boot configuration files on the Options page.
Perhaps removing this additional text wherever it appears in the boot configuration files will help?

Revision history for this message
Cubic PPA (cubic-wizard) said : 		#3

Oops... meant to write "boot=casper" (with an equals sign).

Revision history for this message
Cubic PPA (cubic-wizard) said : 		#4

Were you able to resolve this by removing "boot=casper" ?

Revision history for this message
Alexander Turner (alexturner12) said : 		#5

Hey there! It was actually just me doing stupid things with the distro naming whilst still using the ubuntu repo's. All sorted and nothing to do with Cubic. Thanks for the support and awesome project