Curtinator is not capable of preseeding 18.04 LTS GA

Bug #1767362 reported by Patrick M. Womack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtinator
Invalid
Undecided
Unassigned

Bug Description

Running in an 18.04 ENV, curtinator is not able to preseed the 18.04 image. Image fails to boot with a traceback call.

I will try and grab the traceback, not at the machine at the moment.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Server or desktop? (Desktop, I presume, since curtinator-compatible images for ubuntu server should be available without need of curtinator).

I'll have a look shortly.

Revision history for this message
Patrick M. Womack (ipat8) wrote :

Correct, Desktop. It does find and create a preseed file, but when it goes into kvm to boot the vm it fails to boot.

(I also observe issues with it determining where the preseed file is, but that seems to be resolved with the GA iso, it was primarily a problem with the beta iso.

Revision history for this message
Daniel Manrique (roadmr) wrote :

I would really need to see the errors you get. I just tried this with a freshly-downloaded 18.04 desktop amd64 image which I ran on a computer with i7-4500U CPU , 8GB RAM and about 100 GB of free disk space (and which I've tested can run kvm VMs correctly) and it worked as expected.

I can think of the following:

- Did you ensure kvm/qemu works on this system?
- Do you have enough RAM? curtinator configures the VM with 1.5 GB RAM.
- Do you have enough disk space?

Let me know. Marking incomplete until we have more info.

Thanks for the report!

Changed in curtinator:
status: New → Incomplete
Revision history for this message
Patrick M. Womack (ipat8) wrote :

https://i.imgur.com/4iO73Fr.png

This is a VM, and I have enabled VTXd so it shouldn't be a problem. I will try with a live system when I have a chance (later this evening over here in USA land).

RAM: 4GB
QEMU: Should work, connections and tests pass.
Disk: 40GB.

Revision history for this message
Daniel Manrique (roadmr) wrote :

a kernel panic! great.

I'd definitely suggest checking launching kvm inside the vm , to ensure nesting is working properly. I have seen kernel panics such as this when the memory value for the kvm is too low, but it should NOT be the case here because 1.5 GB is known to work well for Bionic.

Maybe lowering the RAM (edit data/libvirt.xml and edit the memory value to 1048576, exactly 1 GB, then try again) could help. It's really not a config I've ever tried...

Do let me know if running this on bare metal works better.

Revision history for this message
Patrick M. Womack (ipat8) wrote :

What OS were you running when you tried it on your end?

Revision history for this message
Daniel Manrique (roadmr) wrote :

it's Ubuntu 17.10.

Revision history for this message
Patrick M. Womack (ipat8) wrote :

Alright, that explains something, I was running the 18.04 GA, I've moved back to 16.04 and it will boot the VM, but I had to specify the VM name within the script for it to notice that 18.04 had finished installing.

After doing this, curtinator did notice that the system had finished installing, but throws a libguestfs fuse mount point access error. Let me go over fuse and see if that's a problem.

Revision history for this message
Patrick M. Womack (ipat8) wrote :

Resolved the fuse error, issue on my end. I was able to finalize the image.

Not related but do you have a place for feature requests? I'd like to possibly use the minimal install option.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Right here! File a bug with your request and I can evaluate it and triage it as a feature request.

Thanks!

Changed in curtinator:
status: Incomplete → Invalid
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.