[20:01] <dbungert> a7x: if you want to post those autoinstall logs here, I need to step away for a few but can look when I return.  the autoinstall config and /var/log/installer/curtin-install.log are the interesting bits.
[20:23] <a7x> thanks dbungert, I will try to reproduce on a VM first
[21:14] <a7x_> that's funny, I partially reproduced it on VM (it still fails) but the error is a bit different. How to reproduce: use autoinstall on top of a previous proxmox installation.
[21:15] <dbungert> a7x: proxmox is not something I have experience with but if you share the above logs progress might be possible
[21:16] <a7x> any hint on how to export the logs from the VM?
[21:16] <a7x> I have screenshots, not much more without guest
[21:17] <dbungert> can you ssh in?
[21:17] <a7x> let me try
[21:31] <a7x> got it
[21:33] <a7x> @dbungert, this is the only pastebin that didn't create too many issues: https://pastebin.mozilla.org/yDk4wbQr
[21:34] <a7x> (this is still a partial file, the full one was too large)
[21:36] <dbungert> a7x: are you doing manual partitioning with raw storage config?  lvm-partition-data_tdata has path: null, which matches your crash
[21:37] <a7x> let me paste the conf
[21:38] <a7x> https://pastebin.mozilla.org/2PKyJFME/raw
[21:39] <a7x> no storage config, pretty straightforward configuration
[21:39] <dbungert> ok, you have no storage section at all, so subiquity generated a bad storage config.  
[21:39] <dbungert> yea
[21:40] <a7x> . /var/run/cloudinit/ might have info?
[21:41] <dbungert> cloud-init is not the one taking action here, cloud-init just helps get the config to subiquity.  This is a subiquity bug, or at least subiquity related.
[21:43] <a7x> hoped that some of that generated configuration files would be in that directory
[21:43] <dbungert> a7x: would you file a bug https://bugs.launchpad.net/subiquity/+filebug ? the critical details are your autoinstall file (no storage section, so default behavior) and /var/log/installer/block/probe-data.json
[21:44] <a7x> I will, thanks
[21:45] <a7x> I will also try to recover the logs of the original issue (not VM)