<dustymabe>
jlebon: might be something we can write up an issue for and let someone else dig in to? For that particular problem at least it's transient.
<dustymabe>
and explainable
<jlebon>
dustymabe: yup agreed. was mostly looking to see if there was a quickfix possible.
<dustymabe>
+1 :)
<dustymabe>
thank you for digging in, it sure helps when we don't ignore these things
<dustymabe>
for the remaining issues
<dustymabe>
i'm trying to reproduce 2. locally
<travier[m]>
I'll take a look at the liblockfile issue but my afternoon is packed so that might be tomorrow
<dustymabe>
travier[m]: +1 - you might be able to get lakshmi to look at it (I don't see her here on IRC but you might be able to reach her internall)
<jlebon>
looks like it might be specific to rawhide
saqali has joined #fedora-coreos
<dustymabe>
jlebon: this is what happens when rawhide doesn't build for a week :) - we end up with 3+ problems and a larger package set diff to comb through
<guesswhat>
i am trying to implement renovate ( https://docs.renovatebot.com/modules/datasource/#aws-machine-image-datasource ) support, but it does not work out of the box, cuz AMI name is universal for stable/next/testing/dev, for example its trying to bump version from stable to dev ( fedora-coreos-36.20220806.20.0-x86_64 )
<jlebon>
dustymabe: ok that's a helpful tip
<dustymabe>
s/remote/remove
<jlebon>
dustymabe: maybe we should just add the real command on top too. then we don't have to worry about someone forgetting to remove the `-t delete` when doing this. :)
<dustymabe>
jlebon: WFM
<spresti[m]>
Thank you guys for getting this working :)
<dustymabe>
I think there may be an SOP somewhere for this in the infra docs
<jlebon>
spresti[m]: ok, it *should* work now
<spresti[m]>
Thank you!!!!
<dustymabe>
guesswhat: so you're saying the strategy doesn't work because we have 3 streams all named similarly?
<guesswhat>
dustymabe: yes, its like a semver versioning or timestamps
<guesswhat>
some classifier in AMI name would definetly help
<guesswhat>
*definitely
<dustymabe>
should be able to use something like: fedora-coreos-*.3.*-{x86_64,aarch64} ?
<dustymabe>
for stable
<dustymabe>
fedora-coreos-*.2.*-{x86_64,aarch64} for testing
<dustymabe>
fedora-coreos-*.1.*-{x86_64,aarch64} for next
<guesswhat>
yes, but what the "3" number, is it static and reliable ?
<dustymabe>
yes `.3.` is for stable
<dustymabe>
2 for testing
<dustymabe>
1 for next
<guesswhat>
this may work I guess
<dustymabe>
I think aws has a new construct for image families but we haven't looked at them yet
<jlebon>
hmm, it'd be better though to be based on the stream metadata instead
<dustymabe>
jlebon: right, I don't know how this tool works though (if it's capable of that)
<jlebon>
i don't think we'll change our versioning schemes anytime soon, but again, I'd prefer users didn't rely on its exact internal details
<dustymabe>
I agree.. guesswhat - do you you know if there is any way to make that tool query our stream metadata and use that information instead?
<dustymabe>
jlebon: do you know if we have any examples of doing that in the docs?
<jlebon>
guesswhat: we don't know the details of renovatebot, but if there's an easier way for us to provide the stream metadata information, we may consider it
<dustymabe>
and come back to me here with questions
paragan has quit [Quit: Leaving]
<jlebon>
dustymabe, spresti[m]: bumped to 64 manually for now
Betal has joined #fedora-coreos
<dustymabe>
jlebon: do we have a general strategy for how to workaround the issue (i.e. the configuration issue that we hit when we implemented the previous fix) in the future?
<jlebon>
dustymabe: this is the first time we've tried to override something written by the s2i runner. i think the workaround is shipping a startup script that does it imperatively instead.
saqali has quit [Ping timeout: 244 seconds]
<guesswhat>
dustymabe: no, it does not support generic http datasource with json/yaml support
<guesswhat>
but it does support github releases and tags
<guesswhat>
so its gonna work for 90% of tools versioned via gh
<guesswhat>
"tools"
<jlebon>
dustymabe: i think we need a FORCE flag on cosa-build
<dustymabe>
jlebon: like what? I imagine obviously if we hit a builder that already used this quay image then we won't re-download, but if we hit a new builder we'd pull from quay again (not the cluster)
<jlebon>
spresti[m]: ahh yup, you'll want to check off FORCE
<gursewak>
Yep that def looks more comprehensive by having a list of required artifacts for each test and checking all of them in single function call.
<gursewak>
I'll update the PR , thanks:)
jpn has quit [Ping timeout: 245 seconds]
<spresti[m]>
WOW i am hitting a lot of flakes today.
<spresti[m]>
s/./, or am I doing something unexpected? /
<spresti[m]>
* WOW am i hitting a lot of flakes today? or am I doing something unexpected?
<dustymabe>
new failure?
<spresti[m]>
and the rerun of [testing]aarch64 also did
<spresti[m]>
13:52:57 harness.go:1488: mach.Start() failed: machine "f373dc23-2fd8-4347-abb1-2559e1d8a12e" failed basic checks: detected failed or stuck systemd units
<spresti[m]>
13:52:57 qemu-system-s390x: -drive if=none,id=mpath10,format=raw,file=nbd:unix:/var/tmp/mantle-qemu230010716/disk1855253409.socket,media=disk,auto-read-only=off,cache=unsafe: Failed to connect to '/var/tmp/mantle-qemu230010716/disk1855253409.socket': No such file or directory
<dustymabe>
do you know of any that exists? ORR would it be OK for us to create it?
<dustymabe>
GetArtifactByStructName() ?
<jlebon>
dustymabe: i think that would require golang reflection, which is yucky
<jlebon>
bgilbert might have a better idea
<dustymabe>
I basically just want to call GetArtifact("LiveIso") and have it give me back the right thing
jpn has quit [Ping timeout: 245 seconds]
jpn has joined #fedora-coreos
<gursewak>
dustymabe, Also I was wondering whether we can update the error message for GetArtifact() to include the name of the artifact we are looking for?
<bgilbert>
dustymabe: where does the string "LiveISO" come from?
<gursewak>
Is there a reason as to why we want to use "LiveISO" and not just "live-iso"?
<bgilbert>
+1 gursewak
<dustymabe>
yeah I mean we can just use the json names, but it seems a bit unclean
<dustymabe>
for example - we will be calling a function to do a check on an arfifact and then later using the struct name to access it
<dustymabe>
which is fine, just felt awkward
<bgilbert>
dustymabe: I think I'm missing some context
<dustymabe>
yeah.. when gursewak pushes up his code (the missing context) i'll tag you in so you have the full picture
<bgilbert>
+1
bgilbert_ has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
crobinso2 has joined #fedora-coreos
llamma` has joined #fedora-coreos
hank_ has joined #fedora-coreos
aleek has joined #fedora-coreos
ninjanne has joined #fedora-coreos
dustymab1 has joined #fedora-coreos
djinni`_ has joined #fedora-coreos
pwhalen_ has joined #fedora-coreos
bgilbert has quit [*.net *.split]
crobinso has quit [*.net *.split]
nalind has quit [*.net *.split]
mnguyen has quit [*.net *.split]
mnguyen_ has quit [*.net *.split]
aleeku_ has quit [*.net *.split]
hank has quit [*.net *.split]
djinni` has quit [*.net *.split]
dustymabe has quit [*.net *.split]
llamma has quit [Ping timeout: 240 seconds]
nalind has joined #fedora-coreos
mnguyen has joined #fedora-coreos
mnguyen_ has joined #fedora-coreos
justJanne has quit [Ping timeout: 240 seconds]
pwhalen has quit [Ping timeout: 240 seconds]
pwhalen_ is now known as pwhalen
dustymab1 is now known as dustymabe
nalind has quit [Quit: bye]
llamma` has quit [Ping timeout: 240 seconds]
llamma has joined #fedora-coreos
bgilbert_ is now known as bgilbert
_whitelogger_ has joined #fedora-coreos
inflatador_ has quit [Changing host]
inflatador_ has joined #fedora-coreos
miabbott[m] has quit [Ping timeout: 240 seconds]
ccha has quit [Ping timeout: 240 seconds]
rishi has quit [Ping timeout: 240 seconds]
GiuDno[m] has quit [Ping timeout: 240 seconds]
mhayden has quit [Ping timeout: 240 seconds]
mnaser has quit [Ping timeout: 240 seconds]
nbsadminaccount- has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Ping timeout: 240 seconds]
enilflah has quit [Ping timeout: 240 seconds]
inflatador has quit [Ping timeout: 240 seconds]
mnaser_ is now known as mnaser
inflatador_ is now known as inflatador
nbsadminaccount- has joined #fedora-coreos
mhayden has joined #fedora-coreos
crobinso2 has quit [Remote host closed the connection]
mheon has quit [Ping timeout: 268 seconds]
plarsen has quit [Quit: NullPointerException!]
<bgilbert>
guesswhat: to be explicit: the concern is that just because there's a numerically larger image version in AWS, does not mean that anyone should use it
<bgilbert>
guesswhat: we want to be able to instruct new launches to use a previous release, if it turns out that there's a regression in the current one
<bgilbert>
guesswhat: the stream JSON is the canonical source of info