<ikkeT[m]>
i'm a bit confused. First of all, I'm using the same device to install it as to run it, the usb ssd. The example kinda gives impression that I could just modify the rootfs. I also want to add the swap and the pv. Should I not describe the whole partition layout?
<ikkeT[m]>
that's what i had done. the instaructions don't mention anything labelling with stuff with boot
<ikkeT[m]>
yet the installer fails on missing such label
<ikkeT[m]>
"error: System has 0 devices with a filesystem labeled boot"
<ikkeT[m]>
i thought it would create those itself?
<ikkeT[m]>
the filesystems
<ikkeT[m]>
I try adding the filesystems too. Would be nice if the docs had the default there as a start to get modifying from it
<jlebon>
ikkeT[m]: you don't need to redefine the EFI and boot partitions. it looks like you want to (1) add a swap partition, (2) size the root partition, and (3) create a data partition. if you don't need the root partition to be last (for potential growing), you can put swap as 5 and data as 6.
<ikkeT[m]>
is it then enough to leave the partitions 1,2 out of the butane file? so it doesn't need to be "full" configuration, only my personal changes?
<jlebon>
right
<ikkeT[m]>
i try that
<ikkeT[m]>
ok thanks
<jlebon>
if you need to move the rootfs, you need to define the filesystem for it too
<ikkeT[m]>
ok, i start to get this now. So the butane config is only to override stuff, not necessary to list it all
<ikkeT[m]>
it get's kinda overlaid to initial ignition template?
mock has quit [Ping timeout: 240 seconds]
mockgeek has joined #fedora-coreos
<fifofonix>
with the rollout of `test` on newly provisioned nodes only I am finding that my chronyd config is not sticking like it used to.
<fifofonix>
this is very likely because i'm configuring chronyd in a non-standard way. how are people expected to configure their own ntp servers?
mockgeek is now known as mock
<jlebon>
ikkeT[m]: right. ignition in general refuses to delete data unless you tell it to (e.g. for partitions, using wipe_partition_entry)
<jlebon>
fifofonix: we did chrony-related changes recently, so it's possible there's a regression there. how are you defining your NTP servers?
<fifofonix>
seems on newly provisioned nodes a file /run/coreos/sysconfig-chrony is generated incorrectly (tries to merge in my config) whereas on upgraded nodes this doesn't exist.
<ikkeT[m]>
this didn't work. the ignition now created only the partition 4,5 and 6
<ikkeT[m]>
efi and boot partitions didn't get crated, as i didn't have them in partitions. so it didn't merge it into anything
<jlebon>
fifofonix: what platform is this on?
<fifofonix>
aws
<jlebon>
are you providing a chrony config in your Ignition?
<jlebon>
ikkeT[m]: to confirm, you're restarting from a freshly installed disk, right?
<fifofonix>
jlebon: yes, as a /etc/sysconfig/chronyd file (hence my question about how I should be configuring this - perhaps this is not a good way)
<ikkeT[m]>
i have this usb ssd, which i install the installer by sudo coreos-installer install --architecture=aarch64 -f fedora-coreos-37.20230303.3.0-metal.aarch64.raw.xz -i butane.ign $FCOSDISK
<ikkeT[m]>
and i remove that from my laptop, and stick it into raspi and boot it
<jlebon>
ikkeT[m]: you'll want to remove the `wipe_table: true`
<ikkeT[m]>
so it starts from fresh
<ikkeT[m]>
it containst the installer at first boot, right? so the table needs to be wiped, right?
<jlebon>
fifofonix: the canonical way is configuring /etc/chrony.conf, but let me check something else
<ikkeT[m]>
ah, ok, so it doesn't mean wiping the gpt itself, but butane config for it?
<jlebon>
fifofonix: interested in how your changes aren't merged in properly. can you file an issue? but also, i'm not sure how you're using that to set your own NTP server. are you overriding the config file chronyd uses?
<fifofonix>
jlebon: will do that and provide details you're asking for. wanted to make sure you wanted an issue for it first.
jpn has quit [Ping timeout: 264 seconds]
<ikkeT[m]>
pfeeew, it works \o/
<ikkeT[m]>
thank you !
<ikkeT[m]>
this was learning excercise. I didn't understand butane merges config in, and i thought those wipe commands were for the real gpt table
jpn has joined #fedora-coreos
<ikkeT[m]>
now to microshift.....
<jlebon>
fifofonix: that'd be good, thanks. hmm, it might be safer actually to just not touch the chrony config at all if /etc/sysconfig/chrony is modified. at the very least, if it specifies an alternate config file, we shouldn't touch it. but that's a bit hacky to do in bash.
<jlebon>
or it might be enough to have our injected `-f` be first so that it lets itself potentially be overridden. depends on chronyd's arg parsing
<jlebon>
ikkeT[m]: nice!
<ikkeT[m]>
next to hunt instructions to get microshift in
Betal has joined #fedora-coreos
jmarrero has joined #fedora-coreos
gursewak has joined #fedora-coreos
mock has quit [Ping timeout: 276 seconds]
mockgeek has joined #fedora-coreos
mockgeek has quit [Client Quit]
mockgeek has joined #fedora-coreos
mockgeek is now known as mock
jcajka has quit [Quit: Leaving]
apiaseck has quit [Ping timeout: 276 seconds]
michele_ has quit [Read error: Connection reset by peer]