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
bgilbert has quit [Ping timeout: 248 seconds]
_whitelogger has joined #fedora-coreos
rsalveti has quit [Quit: Connection closed for inactivity]
Betal has quit [Quit: WeeChat 3.8]
d10n has quit [Ping timeout: 276 seconds]
d10n has joined #fedora-coreos
d10n has quit [Quit: why all the #hashtags #lol #hackers #overheard]
d10n has joined #fedora-coreos
plundra has quit [Remote host closed the connection]
plundra has joined #fedora-coreos
saschagrunert has joined #fedora-coreos
jpn has joined #fedora-coreos
hotbox has joined #fedora-coreos
jcajka has joined #fedora-coreos
hotbox has quit [Ping timeout: 248 seconds]
hotbox has joined #fedora-coreos
paragan has joined #fedora-coreos
rsalveti has joined #fedora-coreos
vgoyal has joined #fedora-coreos
fifofonix has joined #fedora-coreos
nalind has joined #fedora-coreos
plarsen has joined #fedora-coreos
apiaseck has joined #fedora-coreos
<jlebon> fifofonix: i'm not sure why in your case upgrading nodes are not affected, but based on the code it seems like it should've
<jlebon> dustymabe: good either way. probably not worth it
<fifofonix> jlebon: so, to conclude i'm good with the risk of this going to stable. thanks for asking.
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
saschagrunert has quit [Remote host closed the connection]
<jlebon> fifofonix: +1
jcajka has quit [Quit: Leaving]
<dustymabe> jlebon: mind a quick chat on the upgrade test strategy?
<jlebon> dustymabe: sure
<dustymabe> i'm trying to figure out the most optimal way to A) trigger the test B) get good coverage of past release starting points
<dustymabe> i could do a screen share to illustrate the options better or can chat here
Betal has joined #fedora-coreos
<jlebon> maybe screen share
<dustymabe> will send
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
<dustymabe> apiaseck: I notice you reported an error in the test day results on https://testdays.fedoraproject.org/events/153
<dustymabe> do you mind explaining a bit more your failure scenario?
paragan has quit [Quit: Leaving]
<dustymabe> jlebon: did you open that BZ for mhayden against `google-compute-engine-guest-configs` ?
<jlebon> dustymabe: not yet. was hoping we confirmed first that the udev rules + that script was all we need.
<dustymabe> +1
<apiaseck> dustymabe: Sure - only seeing this now.
<apiaseck> I came across the same problem in the test covering tutorial of the Systemd unit service - also mentioned in the comments
<dustymabe> apiaseck: can you restate what the problem is?
<apiaseck> After following all of the steps required for completion of the `Fedora CoreOS updates` tutorial, i.e : selecting older version of the fcos image as a RELEASE, setting up the butane file with the ssh key, and converting it to butane config...
<apiaseck> after a succesfull virt-install, and while logged in as core@localhost on this machine
<apiaseck> rpm-ostree status is returning in my case an error mentioned in the comment
<apiaseck> Mar 29 11:39:01 localhost.localdomain zincati[1413]: [ERROR zincati::cincinnati] failed to check Cincinnati for updates: client-side error: error sending request for url (https://updates.coreos.fedoraproject.org/v1/graph?basearch=x86_64&os_checksum=fc214c16d248686d4cf2bb3050b59c559f091692d7af3b07ef896f1b8ab2f161&node_uuid=f176c9036b1f44739059f4083adfabf3&os_version=37.20230110.3.1&stream=stable&platform=qemu&group=default): error trying to connect:
<apiaseck> dns error: failed to lookup address information: Temporary failure in name resolution
<dustymabe> ahh
<apiaseck> is it Firewall related?
<dustymabe> apiaseck: I don't think so.
<dustymabe> it might be zincati starting before networking is fully up
<apiaseck> Hmm...
<dustymabe> the problem should resolve itself in 5 minutes time
<apiaseck> I will double check that
<dustymabe> did you leave the system up, by chance?
<dustymabe> apiaseck +1
<apiaseck> Nope...
<apiaseck> But the image and configs are still there ...
<apiaseck> Ok - booting it already - will know in 5 minutes
jbrooks has joined #fedora-coreos
<dustymabe> +1
<apiaseck> Problem sorted, error is gone.
apiaseck has quit [Quit: Leaving]
<dustymabe> aaradhak anthr76 apiaseck davdunc dustymabe gursewak jaimelm jbrooks jcajka jdoss jlebon jmarrero lorbus miabbott nasirhm ravanelli saqali skunkerk walters
apiaseck has joined #fedora-coreos
<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
GingerGeek has quit [Quit: Follow ma Twitter: @GingerGeek]
GingerGeek has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
jpn has quit [Ping timeout: 248 seconds]
bgilbert has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
* dustymabe food
* jlebon also goes for food
apiaseck has quit [Quit: Leaving]
nb has quit [Read error: Connection reset by peer]
nb has joined #fedora-coreos
<dustymabe> fifofonix: want to try out the latest `testing-devel` for that chrony issue? https://builds.coreos.fedoraproject.org/browser?stream=testing-devel&arch=x86_64
<dustymabe> gursewak: any luck figuring out how to run `buildextend-kubevirt` in the pipeline?
<gursewak> hey dustymabe I didn't look into it today yet. Will try running it after lunch:)
<fifofonix> dustymabe: will do a new AMI test. back soon.
jpn has joined #fedora-coreos
fifofonix has quit [Read error: Connection reset by peer]
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 248 seconds]
<jlebon> dustymabe, ravanelli: fyi, i filed https://bugzilla.redhat.com/show_bug.cgi?id=2182865 for the -udev split
<ravanelli> jlebon: ++
fifofonix has joined #fedora-coreos
mheon has joined #fedora-coreos
<walters> hmm where's the code for ensuring that if a root tang pin is active, that we always do networking in the initramfs?
jpn has joined #fedora-coreos
<dustymabe> walters: if memory serves me correctly i think there was something that ensured `rd.neednet=1` was set permanently for those scenarios
<dustymabe> not sure where the code is off the top of my head, though
jpn has quit [Ping timeout: 276 seconds]
<walters> nor the docs
<walters> i can't find it in butane, ignition, fedora-coreos-config or some brute force grepping in the initramfs
jpn has joined #fedora-coreos
daMaestro has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]
gursewak has quit [Ping timeout: 250 seconds]
jpn has joined #fedora-coreos
nalind has quit [Quit: bye for now]
sentenza has joined #fedora-coreos
<bgilbert> walters: yes, but you didn't check coreos-installer :-P
<bgilbert> (rdcore)
<walters> bgilbert: heh of course, thanks!
jpn has quit [Ping timeout: 265 seconds]
gursewak has joined #fedora-coreos
gursewak has quit [Ping timeout: 250 seconds]
gursewak has joined #fedora-coreos
jpn has joined #fedora-coreos
gursewak has quit [Ping timeout: 260 seconds]
jpn has quit [Ping timeout: 260 seconds]
mheon has quit [Ping timeout: 276 seconds]
gursewak has joined #fedora-coreos
vgoyal has quit [Quit: Leaving]
gursewak has quit [Ping timeout: 276 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]