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
mheon has quit [Ping timeout: 268 seconds]
plarsen has quit [Remote host closed the connection]
gursewak has quit [Ping timeout: 260 seconds]
gursewak has joined #fedora-coreos
gursewak has quit [Remote host closed the connection]
gursewak has joined #fedora-coreos
gursewak has quit [Remote host closed the connection]
gursewak has joined #fedora-coreos
gursewak has quit [Remote host closed the connection]
gursewak has joined #fedora-coreos
gursewak has quit [Ping timeout: 256 seconds]
gursewak has joined #fedora-coreos
gursewak has quit [Ping timeout: 256 seconds]
gursewak has joined #fedora-coreos
gursewak has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
gursewak has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
gursewak has quit [Ping timeout: 256 seconds]
misuto has quit [Remote host closed the connection]
gursewak has joined #fedora-coreos
misuto has joined #fedora-coreos
gursewak has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
gursewak has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
plundra has quit [Remote host closed the connection]
plundra has joined #fedora-coreos
b100s has joined #fedora-coreos
hank has quit [Quit: I'M OUT]
hank has joined #fedora-coreos
gursewak has quit [Ping timeout: 256 seconds]
hotbox has joined #fedora-coreos
b1000s has joined #fedora-coreos
b100s has quit [Ping timeout: 268 seconds]
saschagrunert has joined #fedora-coreos
snaipe has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
c4rt0_ has joined #fedora-coreos
c4rt0 has joined #fedora-coreos
b1000s has quit [Ping timeout: 256 seconds]
c4rt0_ has quit [Quit: Leaving]
jpn has joined #fedora-coreos
snaipe has joined #fedora-coreos
b1000s has joined #fedora-coreos
ravanelli has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Client Quit]
nalind has joined #fedora-coreos
mheon has joined #fedora-coreos
fifofonix has quit [Quit: Textual IRC Client: www.textualapp.com]
fifofonix has joined #fedora-coreos
vgoyal has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanell_ has joined #fedora-coreos
ravanel__ has joined #fedora-coreos
ravane___ has joined #fedora-coreos
ravanelli has quit [Ping timeout: 256 seconds]
ravanell_ has quit [Ping timeout: 256 seconds]
ravanel__ has quit [Ping timeout: 260 seconds]
ravanelli has joined #fedora-coreos
ravane___ has quit [Ping timeout: 240 seconds]
<dustymabe> jlebon: I was untagging things yesterday and it seems as if I got the repos in some bad state
<dustymabe> I tried to update the shim package so the one in our distrepo is the one signed by a "newer than F35" signing key
<dustymabe> which it is now
<dustymabe> but rpm-ostree compose isn't happy
<dustymabe> error: Cannot download Packages/s/shim-x64-15.6-2.x86_64.rpm: All mirrors were tried; Last error: Downloading successful, but checksum doesn't match. Calculated: 1ac7b5e92e22eabc6ab3e99516056a76f8c2702b5b2576dbd07456f667ba8b67(sha256) Expected: b8d79af51c8395ebcf84a9011c7fefb5888fa94424788eea9af77c271f1bd51d(sha256)
<dustymabe> I wonder if distrepo somehow does an "incremental" update of the repometadata and didn't pick up this change
<dustymabe> I'll try removing the package from the repo/tag - regenerating the repo (without it) and then re-adding it
<jlebon> dustymabe: ahh nice, just saw that in a CI run
<jlebon> yeah, let's try that
<jlebon> i think we've hit this in the past but don't recall the details
<dustymabe> you don't think it's anything on the rpm-ostree side do you? These CI runs should start completely from scratch, right?
<jlebon> it should, yeah
<jlebon> let me try downloading with dnf to confirm
<dustymabe> The RPM file itself is fine.
<dustymabe> just confirmed that
<dustymabe> i think it's the repo metadata that's off
<jlebon> yeah, agreed
<dustymabe> ok one sec and I'll try to fix
ravanelli has quit [Remote host closed the connection]
<dustymabe> ok the issue should be resolved now
plarsen has joined #fedora-coreos
<jlebon> nice, confirmed
<dustymabe> jlebon: did all of those apply clean?
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
<jlebon> dustymabe: yup
<dustymabe> 👍
snaipe has quit [Ping timeout: 256 seconds]
snaipe has joined #fedora-coreos
gursewak has joined #fedora-coreos
b1000s has quit [Ping timeout: 260 seconds]
hotbox has quit [Ping timeout: 260 seconds]
jpn has quit [Ping timeout: 248 seconds]
<dustymabe> jlebon: the fedora openshift cluster got updated to 4.11
<jlebon> dustymabe: exciting
<dustymabe> which.. i'm not sure we should be testing that at this point
<jlebon> heh had just started looking at that too
<jlebon> yeah, i think short-term it should be fine to disable
<jlebon> we might have to move it to supermin to fix this
<dustymabe> we'll get there eventually
<jlebon> it's so silly though because the container is a thin wrapper around the qcow2. we could almost synthesize the tarball manually
<jlebon> maybe just add onto Adam's PR? or I can if you'd prefer
<dustymabe> I can
<jlebon> +1
Betal has joined #fedora-coreos
hotbox has joined #fedora-coreos
saschagrunert has quit [Remote host closed the connection]
c4rt0 has quit [Remote host closed the connection]
gursewak has quit [Ping timeout: 256 seconds]
gursewak has joined #fedora-coreos
<dustymabe> jlebon: sigh - kubevirt still ran in the CI for https://github.com/coreos/coreos-assembler/pull/3211 - I assume c4rt0 isn't trusted
<dustymabe> i'm just going to merge the PR
<jlebon> dustymabe: ahh, i had reached out to him already to try to fix that
<dustymabe> jlebon: how do you fix it?
<jlebon> his membership isn't public
<dustymabe> ahh - oh well :)
<dustymabe> at least we now have unblocked CI for other PRs
<jlebon> indeed +1
<dustymabe> ravanelli: jlebon: any PRs awaiting some attention from me?
<jlebon> dustymabe: is there a tracker issue for the failures motivating https://github.com/coreos/fedora-coreos-pipeline/commit/fab14eb5f4dd183d954a041db3ac5e066808fdc6 ?
<jlebon> marmijo[m] will look into it
<dustymabe> jlebon: I asked internally a few days ago. I think renata looked at it and apparently we don't run a UEFI+iso-live-login test against 4.9 in the old pipeline
<dustymabe> rather than doing work on 4.9 I suggest we just leave the hack in until 4.9 expires
<dustymabe> the iso-as-disk part of it could benefit from denylist support for testiso
<jlebon> there's still 5 months before it expires. it's also basic functionality that should work. so i think it's worth investigating a bit more before carrying it.
<jlebon> agreed it's not urgent though
<dustymabe> jlebon: unfortunately I just wiped the old pipeline so don't have any logs from the runs where it was failing to paste into an issue
<jlebon> it seemed consistent (IIUC?) so hopefully it's something that can be reproduced locally
<dustymabe> yep definitely
<dustymabe> to me; though - if anyone is installing a new cluster they probably aren't doing it on 4.9
<dustymabe> I can open an issue somewhere if you tell me where
fifofonix has quit [Read error: Connection reset by peer]
<jlebon> +1 thanks!
<dustymabe> jlebon: for that recent grub password CVE - any followups for us?
<dustymabe> do we need a barrier release for anything?
<jlebon> dustymabe: yeah, we need at least one barrier with the migration script before we can yank it out
<jlebon> but it's not time-sensitive (we can keep carrying the script safely)
<jlebon> i think the recent barriers we added for the rebase should suffice
<dustymabe> jlebon: we just added a barrier to `testing`
<dustymabe> yep
<dustymabe> I was replying to ^^
<jlebon> replied!
<dustymabe> jlebon: I think the only piece that won't be covered then is `next` since the barrier we added there was before the grub fix came out
<dustymabe> so we'll need to add a barrier there and then we can drop the migration script
<jlebon> dustymabe: makes sense to me
<dustymabe> ravanelli: marmijo[m]: mind a stamp on ^^
<marmijo[m]> dustymabe: looking
<ravanelli> dustymabe: lgtm
<dustymabe> thanks :)
<dustymabe> marmijo[m]: sorry I clicked merge before you had a chance to look
<marmijo[m]> no worries, lgtm anyway :)
gursewak has quit [Ping timeout: 268 seconds]
<dustymabe> jlebon: do you think it's safe to merge https://github.com/coreos/fedora-coreos-streams/pull/604 or should we wait for bgilbert to return?
<jlebon> dustymabe: did you mean https://github.com/coreos/fedora-coreos-config/pull/2095 ? it should be safe AFAIK
<dustymabe> yeah :)
<dustymabe> ok
<dustymabe> jlebon: for the `Update repo-templates config.yaml` step in https://github.com/coreos/fedora-coreos-tracker/issues/1223 do I need to wait until 37 has hit `stable` or can I do that now?
<dustymabe> it's positioned before `stable` in the checklist
c4rt0 has joined #fedora-coreos
c4rt0 has quit [Remote host closed the connection]
<jlebon> dustymabe: good question. i think we can do that now.
<dustymabe> k
<jlebon> it controls upstream release bits so is technically decoupled from FCOS
<dustymabe> jlebon: knowing what we know now about image streams - does it make sense for us to have this: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/coreos-koji-tagger/templates/imagestream.yml#_4
<dustymabe> I guess if we hit an issue - then with the image stream we can roll back
<jlebon> yeah, rollback would be a reason and if the imagestream is used as a trigger
<jlebon> though who knows whether that'll work if the previous version was already GC'ed by Quay
<jlebon> ("that" = the rollback case)
<dustymabe> jlebon: do you want to handle making sure config-bot gets up to date and I'll handle coreos-ostree-importer and coreos-koji-tagger ?
<jlebon> dustymabe: +1
<jlebon> cool. config-bot automatically rebuilt and redeployed onto f37. pod looks happy. :)
gursewak has joined #fedora-coreos
nalind has quit [Quit: bye]
piwu has quit [Quit: Ping timeout (120 seconds)]
piwu has joined #fedora-coreos
gursewak has quit [Ping timeout: 260 seconds]
plarsen has quit [Remote host closed the connection]
vgoyal has quit [Quit: Leaving]