Closed jlebon closed 2 months ago
Didn't test this at all. Let's see what CI says.
openshift/release PR: https://github.com/openshift/release/pull/51370
(Testing locally as well in parallel now.)
Let's also push a release and add a Quay.io tag before merging this.
Let's also push a release and add a Quay.io tag before merging this.
agree. Ideally we build the next stable
with at least a similar base as to what testing
was done with.
Prow needs https://github.com/openshift/release/pull/51370.
/retest
/test ci/prow/images /test ci/prow/rhcos
@travier: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test images
/test rhcos
Use /test all
to run all jobs.
/test images /test rhcos
CoreOS CI hanging at the cosa fetch --strict
step. Possibly something going wrong with supermin. Prow is timing out, likely because of the same issue but for some reason we're not getting any logs there.
Seems related to virtio-serial writes from the guest side sometimes hanging for some reason. (I.e. writes to /dev/virtio-ports/cosa-cmdout
.)
CoreOS CI hanging at the
cosa fetch --strict
step.
OK, latest commit seems to have fixed it! Looked a bit through git log v8.1.3..v8.2.2
in QEMU to see if anything obvious pops out but didn't see anything.
since we have to run CI again maybe let's update: tests/containers/tang/Containerfile
too.
OK weird, debugging in the pod, it looks like Prow is still hitting the same hanging issue that I thought 7857488
(#3785) fixed. And even more fun, I can't get this hang to reproduce when running manually in the pod. So I think there's a race somewhere and the commit just made it less likely.
Anyway, this now sounds like possibly some bug when combining virtio-serial and stdio. I think I'll just rework this to use a regular serial device instead of virtio-serial since that's obviously way more battle-tested.
OK, ran out of cycles trying to debug this. I've ended having to essentially revert 4eb19f46f, which is unfortunate. But at least it passes CI in both Prow and CoreOS CI.
I think I'll just rework this to use a regular serial device instead of virtio-serial
The problem with this is that it doesn't work on all arches. E.g. on aarch64, adding another --serial
doesn't create a /dev/ttyAMA1
device.
Have some work to try to create a minimal/self-contained reproducer to file a bug, but it's proving trickier than expected.
Since CI already passed on this, let's just merge it in to unbreak CI and get to any other fallout faster.
Some of our upstream CIs (ostree, rpm-ostree) require cosa and FCOS to be on the same release. Ideally we'd fix that but there's details there and we want to move cosa anyway.