rhcos: Pin to previous version #1325
Conversation
Something went wrong with our new build system; looks like broken networking in the initramfs. Pin for now.
openshift-ci-robot
added
the
size/XS
|
/cc @darkmuggle |
|
I verified with a local libvirt run this got my master machine to Ignite again. Going to dive into what changed in the builds now. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
This passed the installer just fine, so if it flakes on e2e tests I vote we force it in. |
|
/hold I don't like the precedent this sets. The installer cannot be the backstop for a CI failure. Give me a few minutes to figure out the next move. I want to hold this for a second though. |
openshift-ci-robot
added
the
do-not-merge/hold
Agreed, and we have plans to fix it. As far as "right now" fixes we could revert the build...it's also ugly. |
Agreed. |
|
We're going to hold here and wait for an OS fix. I'm going to leave this open in case something goes very wrong and we end up needing this change, but I do not intend to merge this at this point. /approve cancel |
Do we have a time estimate on that fix? Even if it's just reverting something, I expect it will take time to build a new image and push it through the RHCOS release pipeline. Are we ok with an org-wide e2e-aws outage while we wait for that? I'm personally fine landing this as a temporary stop-gap, reverting it once the RHCOS pipeline is fixed for this particular issue, and then using #1286 consuming e2e-aws-gated RHCOS pins to avoid issues like this in the future. |
|
It's as soon as possible. In the meantime @darkmuggle is pausing the pipeline and removing the offending build. Yeah, it's not ideal, but as noted before, when there are issues with |
Do we have a time estimate on that? Might be faster than waiting on CI here anyway ;) |
|
He's doing it right now ... My guess is around 10 minutes. |
|
The offending build has been removed, the current pipeline is frozen while we test a fix that just merged to The latest listed image from the pipeline should be stable again. |
|
Latest listed build is |
Something went wrong with our new build system; looks like broken
networking in the initramfs. Pin for now.