ravanelli has quit [Remote host closed the connection]
mheon has joined #fedora-coreos
<lorbus>
Hey team, is there a plan to release a base-oscontainer for aarch64 to quay too? I see that's done for the x86 stream, but I don't see it on any other arches
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Read error: Connection reset by peer]
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Read error: Connection reset by peer]
ravanelli has joined #fedora-coreos
<dustymabe>
lorbus: soon enough
ravanelli has quit [Remote host closed the connection]
<lorbus>
ok, just wanted make sure it's on the radar :)
<dustymabe>
we'll update it to be multi-arch when we switch to the new quay repo
<lorbus>
dustymabe: Perfect, thank you!
bgilbert has joined #fedora-coreos
aleskandro[m] has joined #fedora-coreos
<lorbus>
cc aleskandro
<dustymabe>
jlebon: are you able to get to the pipeline right now?
<dustymabe>
i'm getting an ssl issue
<dustymabe>
"jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site."
<dustymabe>
oh, the certificate expired
<dustymabe>
fun
* dustymabe
heads over to #fedora-admin
<jlebon>
dustymabe: yup can confirm
<dustymabe>
they are looking into it
<jlebon>
+1
crobinso has quit [Ping timeout: 268 seconds]
jpn has quit [Ping timeout: 255 seconds]
jpn has joined #fedora-coreos
gursewak has joined #fedora-coreos
<dustymabe>
jlebon: FYI - the cert issue has been fixed
<jlebon>
dustymabe: just noticed. thanks!
jcajka has quit [Ping timeout: 252 seconds]
<jlebon>
dustymabe: requesting lock on stage pipeline
<dustymabe>
granted()
SandipanRoy[m]1 has quit [Quit: You have been kicked for being idle]
<dustymabe>
ravanelli: once the build passes do you think you could try it out in the 3.11 cluster to prove that we don't break RHCOS ppc64le builds (as a result of https://github.com/coreos/coreos-assembler/pull/3033)
skunkerk has joined #fedora-coreos
mnguyen_ has quit [Ping timeout: 252 seconds]
mnguyen has quit [Ping timeout: 268 seconds]
mnguyen has joined #fedora-coreos
mnguyen_ has joined #fedora-coreos
jpn has quit [Ping timeout: 255 seconds]
<dustymabe>
jlebon: do you know what happens if we don't set `currentBuild.result = 'SUCCESS'` in the pipeline jobs?
<dustymabe>
will it automatically default to success (assuming something else doesn't set it to FAILURE)
<dustymabe>
i'm trying to go through and fix the pipeline to not send a slack FAILURE message when the upgrade test fails (which was allowed by the user)
<dustymabe>
but to send a warning instead
<dustymabe>
actually thinking about it now, i'm not sure I quite understand how it works