dustymabe changed the topic of #fedora-coreos to: Fedora CoreOS :: Find out more at https://getfedora.org/coreos/ :: Logs at https://libera.irclog.whitequark.org/fedora-coreos
dustymabe has quit [Quit: WeeChat 3.6]
dustymabe has joined #fedora-coreos
bgilbert has quit [Ping timeout: 255 seconds]
vgoyal has quit [Ping timeout: 246 seconds]
daMaestro has joined #fedora-coreos
plarsen has quit [Quit: NullPointerException!]
paragan has joined #fedora-coreos
Turnikov has quit [Ping timeout: 268 seconds]
paragan has quit [Ping timeout: 246 seconds]
paragan has joined #fedora-coreos
paragan has quit [Quit: Leaving]
Betal has quit [Quit: WeeChat 3.7.1]
jcajka has joined #fedora-coreos
Skriptum-M[m] has quit [Quit: You have been kicked for being idle]
jpn has joined #fedora-coreos
daMaestro has quit [Quit: Leaving]
c4rt0 has joined #fedora-coreos
c4rt0 has quit [Remote host closed the connection]
c4rt0 has joined #fedora-coreos
c4rt0 has quit [Read error: Connection reset by peer]
Turnikov has joined #fedora-coreos
llamma has joined #fedora-coreos
c4rt0 has joined #fedora-coreos
fifofonix has joined #fedora-coreos
<dustymabe> c4rt0: do you think you could pick this up? https://github.com/coreos/fedora-coreos-docs/issues/491
<dustymabe> there are two things to do there update site.yml as described in https://github.com/coreos/fedora-coreos-docs/issues/491#issuecomment-1370164087 and then we circle back to see if the original described issue is fixed
<dustymabe> jlebon: it's odd to me that CI tests are failing on https://github.com/coreos/fedora-coreos-config/pull/2151
<dustymabe> Found kernel panic (VFS: Unable to mount root fs on unknown-block(0,0)
<dustymabe> ) on machine d50c03d4-c6e8-4f55-9332-0a44d8f0312b console
<dustymabe> but we literally just built and released these RPMs in the release rolling out now
<dustymabe> maybe some issues with the hardware in our CI?
<c4rt0> test
<dustymabe> test worked
<dustymabe> :)
<c4rt0> :) ok - now I know what it was.
<c4rt0> Just for reference - will pick it up with pleasure - thanks Dusty
<dustymabe> thanks c4rt0
Betal has joined #fedora-coreos
<dustymabe> anybody able to take this NetworkManager issue on Azure and try to find the root cause and open an issue upstream? https://github.com/coreos/fedora-coreos-tracker/issues/1341
<jlebon> dustymabe: i think that error is either due to not enough memory, or a corrupted initrd which sounds more unlikely
bgilbert has joined #fedora-coreos
Turnikov has quit [Ping timeout: 252 seconds]
plarsen has joined #fedora-coreos
<dustymabe> jlebon: so we need to bump the memory in CoreOS CI?
<dustymabe> aaradhak anthr76 davdunc dustymabe gursewak jaimelm jbrooks jcajka jdoss jlebon jmarrero lorbus miabbott nasirhm ravanelli saqali skunkerk walters
<dustymabe> FCOS community meeting in #fedora-meeting-1
<dustymabe> If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt
marmijo has joined #fedora-coreos
marmijo has quit [Client Quit]
<jlebon> dustymabe: it'd be the base memory of the test VMs on x86_64 (i.e. from 1G), which would be unfortunate. let's dig into it more before doing that
jcajka has quit [Quit: Leaving]
vgoyal has joined #fedora-coreos
Nemric has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
<stephanepoq> I would like to try: k3s or MicroK8s (on Fedora coreOs), any recommendation on that question?
Nemric has quit [Quit: WeeChat 3.7.1]
<dustymabe> stephanepoq: you might ask on the discussion forum to see if there are some folks who have recommendations there
<dustymabe> marmijo[m]: gursewak: anyone want to take a stab at trying to figure out why `rawhide` is failing builds?
<stephanepoq> tried to roll the dice here ;-), otherwise I pick one by chance
gursewak_ has joined #fedora-coreos
gursewak has quit [Ping timeout: 252 seconds]
<marmijo[m]> dustymabe: I'll look into it
jpn has joined #fedora-coreos
<jlebon> dustymabe: fyi: https://github.com/coreos/fedora-coreos-tracker/issues/1352#issuecomment-1371269284. will fast-track and unpin cosa after food
Turnikov has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
<marmijo[m]> dustymabe: I opened a new issue about the `rawhide` failures. https://github.com/coreos/fedora-coreos-tracker/issues/1369
<dustymabe> jlebon: nice! you mean "unpin grub2" right?
<dustymabe> marmijo[m]: nice. Thanks for the investigation!
<dustymabe> bgilbert: jlebon: should we include LibVirt and QEMU in our platforms list (i.e. if we're requesting VMWare and VirtualBox)?
<jlebon> dustymabe: i mean unpin grub2 in cosa
<dustymabe> jlebon: it's unpinned already
<dustymabe> when we moved to f37
<dustymabe> it IS pinned in FCOS, though
<jlebon> right, need to unpin in both
<dustymabe> weird
<dustymabe> I thought we dropped that pin
<jlebon> we dropped the pin for the ppc64le issue when we rebased, but added a new independent pin for the EFI issue
<dustymabe> oh haha
<dustymabe> right
<dustymabe> because we ARE using the grub from the target system now, BUTT there are some tests that use the grub from COSA still (like the PXE test)?
<jlebon> yup, exactly!
<dustymabe> ok. but for the COSA change we're going to have to manage it
<dustymabe> i.e. we don't want our next `stable` build to fail because we no longer have grub pinned in COSA
<dustymabe> we could tag COSA
<dustymabe> in quay
<jlebon> hmm, is that necessary though? the grub in the next cosa build works fine
<dustymabe> oh I see what you're saying
<dustymabe> yeah I think you are right
<dustymabe> ignore me :)
<jlebon> :)
<dustymabe> I think my qestion from earlier got overlooked so I'll ask again..
<dustymabe> bgilbert: jlebon: should we include LibVirt and QEMU in our platforms list (i.e. if we're requesting VMWare and VirtualBox)?
jpn has joined #fedora-coreos
<jlebon> dustymabe: hmm, not sure. i wonder if it's obvious and so wouldn't add value there
<jlebon> also libvirt supports more than just QEMU, so it might be confusing to have both there.
c4rt0 has quit [Quit: Leaving]
<bgilbert> I'd say yes to QEMU, but libvirt is an abstraction layer
jpn has quit [Ping timeout: 272 seconds]
<dustymabe> K
jpn has joined #fedora-coreos
<dustymabe> jlebon: any idea why the `testing` and `next` tabs on the release notes page won't load?
<dustymabe> at least it won't load for me
jpn has quit [Ping timeout: 268 seconds]
<dustymabe> ok figured it out - see first commit in https://github.com/coreos/fedora-coreos-streams/pull/627
jpn has joined #fedora-coreos
<dustymabe> marmijo[m]: are you good to do this (and possibly move to the openshift/os repo for RHCOS)? https://github.com/coreos/fedora-coreos-tracker/issues/1369#issuecomment-1371330232
<jlebon> dustymabe: looks like we're hitting a TypeError in coreos-release-notes.js (looking at the console)
<marmijo[m]> dustymabe: sure thing, I'll work on that.
<jlebon> we really need a basic CI check on this
<dustymabe> jlebon: I think I fixed it in the first commit in https://github.com/coreos/fedora-coreos-streams/pull/627
<jlebon> dustymabe: yup, saw that after.
<dustymabe> marmijo[m]: mind a review on https://github.com/coreos/fedora-coreos-streams/pull/627 since you're around?
jpn has quit [Ping timeout: 260 seconds]
<marmijo[m]> dustymabe: LGTM!
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
<dustymabe> jlebon: do you want to respond to the latest request in https://bugzilla.redhat.com/show_bug.cgi?id=2154428 or do you want me to?
* dustymabe heads out for a bit - be back later tonight
<jlebon> dustymabe: yeah, it was on my backlog to do. will tackle it tomorrow if you don't get to it before me :)
<dustymabe> i'm cool either way - just don't want to dupe - if I don't do it tonight then I'll let you do it tomorrow, how about that?
<jlebon> sgtm
ravanelli has quit [Ping timeout: 252 seconds]
cyberpear has joined #fedora-coreos
vgoyal has quit [Quit: Leaving]