Please test autoinstalls for 20.04!

[mwhudson]

@bnason

So after debugging this a whole bunch more it is now working, just not like I expected. It seems the installer doesn’t actually create the user. Instead it creates a cloud-init config to be used at first startup. Is this accurate?

Yes.

I had a late-command in the autoinstall config that was disabling cloud-init which is why the user wasn’t being created.

Yep, that would do it.

@bnason

Maybe this was a bug with the 20.04 iso and it got fixed in 20.04.1 because I can’t seem to reproduce it any more.

Possibly, I don’t think anything changed around this but oh well. Get me logs if it starts happening again please!

@bnason

My only issue now is I can’t get the installer to NOT create swap. I have the following in my config. Is layout direct conflicting with swap size 0? Is there a way to specify effectively: fill entire disk, don’t use lvm and no swap.

  storage:
    swap:
      size: 0
    layout:
      name: direct

Ah, looks like the swap key is ignored if you use a layout option. That would be a bug, sorry.

@thaddeus-wh

So it looks like it’s looking at the url param for cloud-config ?
Anyone got any pointers? Thanks

Sign it does look like cloud-init config looks at url= in the kernel command line (I didn’t know this!), but the s= url should still be looked at as well. Can you post any more logs?

@bruteforceattack

Does anybody know how can I change default filesystem type? It is possible via system installer guide (supports: xfs, ext4 and brtfs), so I believe that there must be a key for that. All I want is to install ubuntu with lvm (default layout: name: lvm) but with xfs as filesystem type.
Please don’t tell me that I need to do it manually I mean define all the partions like it is mentioned above (look for EFI customization)

Currently the layout options do hardcode ext4 filesystem I’m afraid. This should be easy to fix though, can you file a bug on Launchpad?

@matthew.williams

Which is just stuck at connecting forever, when stopped with ctrl + c it displays the message below and starts over.

You must be using edge? I guess you should stop doing that for the moment, some disruptive changes are landing. It should still be working so I’ll try and fix it, but if you use edge it’s going to break from time to time, realistically.