saschagrunert has quit [Remote host closed the connection]
dustymabe has quit [Ping timeout: 248 seconds]
dustymabe has joined #fedora-coreos
<apollo13>
mhm, error: 'units' directive is incompatible with machineid-compat = false -- but machineid-compat is set to false because: "# Required by Ignition, and makes the system not compatible with Anaconda"
<apollo13>
so how do I enable units by default?
<apollo13>
aha presets I need
jpn_ has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
go4godvin has quit [Quit: You have been kicked for being idle]
jpn has joined #fedora-coreos
jpn_ has quit [Ping timeout: 255 seconds]
<dustymabe>
apollo13: sorry - our ostree expertise is a little light this week
<apollo13[m]>
No worries I worked around most issues. What I would be interested in though: where are the actual CI configs that build coreos releases as opposed to the .dev releases that pop out of the repo
<apollo13[m]>
What does /proc/cmdline tell you? I'd expect some hints there
<dustymabe>
i went for a half backport here because the updated azure libraries use golang features that aren't supported in the golang version on the older branches
<jdoss>
I am going to spam your DMs with these screenshots since I can't copy off this IPMI console.
<jdoss>
These are new drives, pretty sure there is no boot sector protection.
<bgilbert>
got em
<bgilbert>
so what I'm seeing is that the drives all have empty partition tables
<bgilbert>
and your config wipes all of the tables and doesn't have any partitions numbered higher than 2
<bgilbert>
and so I'm confused about two things
<bgilbert>
1) where's your OS disk? 2) why is it complaining about being unable to change partition 3?
<jdoss>
No clue. The OS disk is root-raid
<bgilbert>
oh, sorry, I missed the boot_device sugar
<bgilbert>
okay
<bgilbert>
your config is giving contradictory instructions again
<bgilbert>
if you run it through butane -p, you'll see that you're asking for two root partitions on each of the root disks, with different names and numbers
<jdoss>
I am confused. I am trying to make 2x RAID 1 setups. The first is the 500GB drives in RAID 1 with root and home partitions, then a 2TB /opt in RAID 1
<bgilbert>
right
<bgilbert>
but you're trying to override the boot_device sugar in contradictory ways
<bgilbert>
you probably do need to override it a bit, to set the size of the root partitions
<bgilbert>
but you're trying to renumber the root partition and give it a different name
<bgilbert>
and then define the RAID again
<jdoss>
Errm, I run it through butane -p and it just kicks out the ignition without any complaints.
<bgilbert>
yeah, it doesn't second-guess you, but if you read the config it doesn't really make sense
<jdoss>
Yah I am not seeing what you are seeing.
<bgilbert>
well, let me back up. why are you using boot_device.mirror and also hand-defining the root RAID?
<jdoss>
omg, I have an old config. bgilbert forgive me.
<bgilbert>
heh, np
baude has quit [Remote host closed the connection]