<dustymabe>
bgilbert: i wonder if this is something we should collaborate with them on and utilize as a tool for our community too
<decfi[m]>
<travier[m]> "decfi: Why are you expecting..." <- My use case is pretty simple. On a bare metal server I'd like to provision Fedora CoreOS with two encrypted volumes, root and data. I expect coreos-installer to mount the LUKS encrypted partition with the help of the configured tang server (tang works fine... (full message at <https://libera.ems.host/_matrix/media/r0/download/libera.chat/e215668ce1ac9de95c55f0030896991120a25f55>)
<travier[m]>
decfi: If I understand you setup correctly, you're trying to setup LUKS and then use coreos-installer. It's not how things work on Fedora CoreOS. You install directly with no previous setup with coreos-installer passing the ignition config and then LUKS gets set up by ignition on first boot
<travier[m]>
s/you/your/
<decfi[m]>
<travier[m]> "decfi: If I understand you setup..." <- Sorry, I wasn't clear enough. I don't setup LUKS before, I wipe the disks in the ignition config. My data volume `/dev/sdb` is on a usb drive and the mount path is `/var`. For testing I setup the root volume without LUKS
<decfi[m]>
`ignition-disks.service` fails on `var.mount`
bgilbert has quit [Ping timeout: 260 seconds]
<travier[m]>
This is only part of the picture. It does not tell us how you do the installation, etc. Again, I recommend that you post something detailed on the forum
<dustymabe>
marmijo: the azure run failed - looks like an infrastructure flake - we can accept these results as good since the failed test passed in a re-run.
<marmijo>
dustymabe: Thanks, I updated the issue with that info.
<marmijo>
pull 116 LGTM!
<marmijo>
I'll wait until tomorrow morning to run the release job
<dustymabe>
marmijo: I need to run but I can review the rollout PR in the morning (you can also finish up any further release steps in the morning) - we're ahead of the ball this week so we don't have to rush