[11:56] <mup> Bug #1993289 opened: Pod storage pool path can't be blank <MAAS:In Progress by ack> <MAAS 3.1:In Progress by ack> <MAAS 3.2:In Progress by ack> <https://launchpad.net/bugs/1993289>
[11:59] <mup> Bug #1993289 changed: Pod storage pool path can't be blank <MAAS:In Progress by ack> <MAAS 3.1:In Progress by ack> <MAAS 3.2:In Progress by ack> <https://launchpad.net/bugs/1993289>
[12:02] <mup> Bug #1993289 opened: Pod storage pool path can't be blank <MAAS:In Progress by ack> <MAAS 3.1:In Progress by ack> <MAAS 3.2:In Progress by ack> <https://launchpad.net/bugs/1993289>
[13:44] <shubjero> Hey all. I've got some servers to deploy which have 2x1TB nvme drives which I'd like to deploy as raid-1 w/ lvm on top and efi boot. I can configure what I think is a valid config in MaaS but upon server deployment it fails to apply that storage config.
[13:44] <shubjero> Anyone know of any guides on this?
[13:44] <shubjero> I can provide more detail / screenshots / logs
[13:50] <shubjero> https://imgur.com/a/qlwJWmu - here is the disk layout I am attempting
[13:50] <shubjero> im deploying it now just so i can get the error message again
[13:58] <shubjero> https://paste.openstack.org/show/bbVUQqH123FJeFNvhngy/
[13:58] <shubjero> there's the error
[14:00] <shubjero> this happened on maas 2.8 and so i thought it was prudent to upgrade to newer maas but still happens on 3.2
[14:56] <ahasenack> you have /boot/efi in lvm? Is that allowed?
[14:57] <ahasenack> I don't think the BIOS understand lvm
[17:15] <shubjero> ahasenack: ive also tried /boot/efi outside of lvm as a regular partition. I will try that again, screenshot, and check logs too
[17:15] <shubjero> give me a few
[18:03] <ahasenack> I thought maas would take care of /boot/efi, I don't recall in detail
[18:03] <ahasenack> maybe it doesn't
[18:25] <shubjero> maas seems to let you do varying storage schemes that just dont work