[00:00] <kenyon> leftyfb: also I would switch to another console when it stops for confirmation and look at the subiquity logs, maybe that'll help figure out why it's prompting
[00:10] <leftyfb> wtf
[00:10] <leftyfb> https://i.imgur.com/RmOGYZ1.jpeg
[00:10] <leftyfb> it starts to tell the reason then cuts off
[00:11] <leftyfb> "subiquity/Meta/status_GET: SUCCESS: 200 {"state:": "NEEDS_CONFIRMATION", "confirming_tty": "", "error": null, "cloudi...
[00:13] <leftyfb> the client log is equally useless https://i.imgur.com/i95DQwZ.png
[00:13] <leftyfb> this is giving the name: a name
=== chris14_ is now known as chris14
=== mybalzit1h is now known as mybalzitch
=== ch0ps3y is now known as Guest7028
[15:21] <leftyfb> kenyon: ok, just did a quick test. I copied the autoinstall-user-data file from a server, removed the serial# matching and kicked off the install. It went fine with no prompts at all. The problem is, if I set the network to interactive as I need, then it will still prompt with the "confirm destructive actions"
[15:22] <leftyfb> I think no matter what, if you have anything that is interactive, it's going to prompt you for that
[20:47] <MTecknology> Does anyone know anything about breaking changes between the installer for ubuntu 20.04 and 22.04? I can use the exact same autoinstall for either, but 22.04 seems to bomb on a python KeyError.
[20:50] <MTecknology> I'm hoping it's as simple as some new key being required, but I can't find any documentation for what that would be.
[21:12] <sarnold> MTecknology: I *think* I heard that incorrect configs that might have been silently accepted are now noisier, but I can't recall details :(