You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we don't have anything that ensures we stabilize a Butane openshift spec every OCP release cycle. Per discussion with @dustymabe, we could add a test so we don't forget to do this.
Butane is invoked by users, not by tools, and the user also selects the spec to be used. Also, Butane isn't in the OS or the release payload, nor does it have a downstream container image. As a result, figuring out what to check isn't completely trivial.
Proposal:
Compute the OCP version from the RHCOS version.
Generate an openshift Butane config with a non-experimental version matching the OCP version.
See if the config transpiles. In Git master, it probably never will, assuming RHCOS is branched before Butane stabilizes the new spec. But in the release branch, it eventually will, late in the OCP development cycle.
Use a snooze to disable the test until after the expected spec stabilization date. When tests fail on master, bump the snooze. When they fail on the branch, there's an actual problem.
This is all a bit awkward, though, since it would fail RHCOS builds solely to draw attention to an unrelated problem.
The text was updated successfully, but these errors were encountered:
Currently we don't have anything that ensures we stabilize a Butane
openshift
spec every OCP release cycle. Per discussion with @dustymabe, we could add a test so we don't forget to do this.Butane is invoked by users, not by tools, and the user also selects the spec to be used. Also, Butane isn't in the OS or the release payload, nor does it have a downstream container image. As a result, figuring out what to check isn't completely trivial.
Proposal:
openshift
Butane config with a non-experimentalversion
matching the OCP version.master
, it probably never will, assuming RHCOS is branched before Butane stabilizes the new spec. But in the release branch, it eventually will, late in the OCP development cycle.master
, bump the snooze. When they fail on the branch, there's an actual problem.This is all a bit awkward, though, since it would fail RHCOS builds solely to draw attention to an unrelated problem.
The text was updated successfully, but these errors were encountered: