<bgilbert>
jdoss: if you run that through Butane, you'll see it produces a bit of a mess wrt partition tables
<bgilbert>
you have some redundant stuff in there
<bgilbert>
Butane will let you do some overriding of the desugared output, but you have to match it
<bgilbert>
I'd drop the wipe_table on the rootfs disks (technically correct, but confusing) and the start_mib and number on raid-root-1, then rename it to root-1 to match Butane
<bgilbert>
doesn't work, hmm
<jdoss>
updated that gist
<bgilbert>
does work; I had typoed my copy
<jdoss>
Story of my life.
<bgilbert>
oh, and stop defining fcos-root
<bgilbert>
raid or filesystem. Butane will do that
<jdoss>
Remove the filesystem directives for fcos-root
stephanepoq has quit [Quit: Konversation terminated!]
linux-modder has quit [Remote host closed the connection]
vgoyal has joined #fedora-coreos
linux-modder has joined #fedora-coreos
linuxmodder has quit [Ping timeout: 248 seconds]
<aleskandro[m]>
hello, some time ago, I overrode the kernel package to use in an installation via rpm-ostree override replace --experimental --from repo=..... Now, I want to upgrade to a new base image that ships a new kernel and I get into an error as the new kernel packages conflict with the layered ones. The update is being done from a base image to the new one available in a remote registry with rpm-ostree update (ie., not rebasing to a
<aleskandro[m]>
new image-tag pair). Is there a specific procedure I should follow to avoid removing the layered kernel, upgrade and layering again?
Turnikov has quit [Read error: Connection reset by peer]
Turnikov has joined #fedora-coreos
linux-modder has quit [Ping timeout: 252 seconds]
cybercrypto has quit [Remote host closed the connection]
Guest8245 has joined #fedora-coreos
Guest8245 is now known as linux-modder
cybercrypto has joined #fedora-coreos
Turnikov has quit [Ping timeout: 248 seconds]
<travier[m]>
aleskandro: If you have a local override and want to use the new kernel from the new image then you need to rpm-ostree override reset to remove the local override
Turnikov has joined #fedora-coreos
linux-modder has quit [Ping timeout: 255 seconds]
Guest2960 has joined #fedora-coreos
Guest2960 is now known as linux-modder
linux-modder has quit [Client Quit]
Guest1659 has joined #fedora-coreos
Guest1659 is now known as linux-modder
linux-modder is now known as linuxmodder
jpn has joined #fedora-coreos
<aleskandro[m]>
Hi travier I don't want to use the new kernel but want to keep on that. It's actually a remoteOverride, not a local one
<aleskandro[m]>
s/that/the version I overrode with/
mheon has joined #fedora-coreos
Guest281 has joined #fedora-coreos
linuxmodder has quit [Killed (calcium.libera.chat (Nickname regained by services))]
Guest281 is now known as linuxmodder
nalind has joined #fedora-coreos
linuxmodder has quit [Client Quit]
Betal has joined #fedora-coreos
Guest8389 has joined #fedora-coreos
Guest8389 is now known as linuxmodder
jlebon has joined #fedora-coreos
gursewak has joined #fedora-coreos
Turnikov has quit [Ping timeout: 260 seconds]
Turnikov has joined #fedora-coreos
<travier[m]>
aleskandro: I don't understand what you have, what you're pulling, what you want. Maybe you should write a more descriptive post on the forums so that we can answer that
linuxmodder is now known as Guest2388
Guest2388 has quit [Killed (cadmium.libera.chat (Nickname regained by services))]
linuxmodder has joined #fedora-coreos
Guest2388 has joined #fedora-coreos
linuxmodder has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
Guest2388 is now known as linuxmodder
linuxmodder is now known as Guest9048
Guest9048 has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
linuxmodder has joined #fedora-coreos
Guest9048 has joined #fedora-coreos
linuxmodder has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
Guest9048 is now known as linuxmodder
linuxmodder is now known as Guest9905
Guest9905 has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
linuxmodder has joined #fedora-coreos
Guest9905 has joined #fedora-coreos
linuxmodder is now known as Guest9736
Guest9905 is now known as linuxmodder
saschagrunert has quit [Remote host closed the connection]
fifofonix has joined #fedora-coreos
daMaestro has joined #fedora-coreos
gursewak has quit [Ping timeout: 248 seconds]
gursewak has joined #fedora-coreos
jcajka has quit [Quit: Leaving]
nalind has quit [Ping timeout: 252 seconds]
nalind has joined #fedora-coreos
gursewak has quit [Ping timeout: 248 seconds]
bgilbert has joined #fedora-coreos
<miabbott[m]>
hey folks, i tried building RHCOS 4.13 for the first time in a long while and noticed that `cosa build` and `cosa run` took a lot more time than what i remember. notably the `ostree container encapsulate` step during `cosa build` took nearly 15min.
<miabbott[m]>
i know there are a lot of variable that can affect performance, but i'm curious if there are some changes to `cosa` that i might have missed which could have caused this? otherwise, i'll just assume that my system is to blame
<jlebon>
miabbott[m]: hmm, nothing offhand that comes to mind. are you sure you have kvm?
<miabbott[m]>
i'll have to double check...might be a side effect of rebasing to F37 SB, but that seems suspicious
<miabbott[m]>
it's been a long time since i did any `cosa` operations and i did cleanup some things in my home directory...seems likely it is an issue with my environment
jpn has quit [Ping timeout: 268 seconds]
<miabbott[m]>
hmm...looks like i made some changes to my cosa alias that could have affected perf...using the alias from the docs in a clean repo was much faster
<dustymabe>
jlebon: spresti[m] (as an FYI): the issue that we're hitting is `couldn't publish image in ap-southeast-3:` because `ResourceLimitExceeded: You have reached your quota of 208 for the number of public images allowed in this Region`
<dustymabe>
the limit is pretty low there as compared to other regions IIUC
<dustymabe>
for now I just went through and marked our f35 AMIs in that region as private
<dustymabe>
but really this gets back into the GC discussion, which we need to prioritize
<jlebon>
interesting. didn't realize different regions had different quotas
<jlebon>
yup, definitely
Turnikov has joined #fedora-coreos
<spresti[m]>
Yeah that certainly is a low number.
<dustymabe>
I just opened up like 60 slots for us :0
ccha has quit [Quit: WeeChat 3.7.1]
ccha has joined #fedora-coreos
<dustymabe>
spresti[m]: if you want maybe we should add a comment in the streams issues about why we skipped the openstack tests requirement (i.e. VexxHost infra issues)
<dustymabe>
that has an open support ticket
<spresti[m]>
Ok will do
<spresti[m]>
Can I get a link to the @support ticket or is it non public?
<jlebon>
PSA: Planning to update CoreOS CI tomorrow to roll out https://github.com/coreos/coreos-ci/pull/47. Upstream CI will not run while it's down, though it shouldn't be for too long (unless something goes wrong of course :) ).
linuxmodder has quit [Quit: Leaving]
Turnikov has quit [Ping timeout: 248 seconds]
nalind has quit [Quit: bye for now]
Turnikov has joined #fedora-coreos
fifofonix has quit [Ping timeout: 265 seconds]
Turnikov has quit [Ping timeout: 248 seconds]
Turnikov has joined #fedora-coreos
Turnikov has quit [Read error: Connection reset by peer]