Description of problem:
in MCO release-4.1 branch we aren't pinning verify tools and always pulling from latest master for tools caused a bad breakage where we cannot compile those tools with go1.10 anymore (1.10 is what 4.1 is pinned to).
Seen in https://github.com/openshift/machine-config-operator/pull/1121 and https://github.com/openshift/machine-config-operator/pull/1119
The fix is pinning the tools as doing in https://github.com/openshift/machine-config-operator/pull/1132 and https://github.com/openshift/release/pull/5162
Version-Release number of selected component (if applicable):
4.1 release branch
Steps to Reproduce:
1. open a PR against 4.1 release branch in MCO
Please clone the bug to 4.1.z, ensure it doesn't need to be fixed in 4.2 and 4.3. If it's confirmed the issue doesn't exist in any release > 4.1.z, go ahead and close those clones after the fix is verified from 4.1.z onward.
We've been discussing this on slack for the past few days - this bug is _only_ in the 4.1 CI and it doesn't make sense to have a 4.2 or later BZ cause it's of course working - do we really need fake BZs just to track something it's not even in >4.1 releases for a bug which is just 4.1? I find that time-wasting. I understand perfectly the process but this doesn't fall into the process per-se since we're not risking a regression in newer releases (or old ones for that matter). This is again just a 4.1 issue and 4.2/master CI is _of course_ working well.
the label on the pr is failing bc this doesn't target 4.1.z, can we update @Antonio?
This BZ is now blocking another PR: https://github.com/openshift/machine-config-operator/pull/1140
Ian created the other BZs as well
This now has a 4.2.z BZ in Depends on, moving to 4.1.z
Checking a PR to `release-4.1` after this fix was merged shows that the verify job is working properly - https://github.com/openshift/machine-config-operator/pull/1121
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.