Bug 2042534

Summary: Bump build-machinery-go for console-operator to pickup change in yaml-patch repository
Product: OpenShift Container Platform Reporter: Jakub Hadvig <jhadvig>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Xiyun Zhao <xiyuzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, xiyuzhao
Target Milestone: ---   
Target Release: 4.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-16 11:19:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2041359    
Bug Blocks:    

Description Jakub Hadvig 2022-01-19 16:32:52 UTC
This bug was initially created as a copy of Bug #2041359

I am copying this bug because: 
Need release-4.7 backport

Description of problem:
there is an issue with yaml-patch tool which was moved from:
https://github.com/krishicks/yaml-patch
to:
https://github.com/pivotal-cf/yaml-patch

due to this issue "ci/prow/verify" is failing for PR  <= 4.9


Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Check console-operator PR <= 4.9
2.
3.

Actual results:
ci/prow/verify  on console-operator repo is failing with:
```
curl -s -f -L https://github.com/krishicks/yaml-patch/releases/download/v0.0.10/yaml_patch_linux -o '_output/tools/bin/yaml-patch-v0.0.10'
make: *** [ensure-yaml-patch] Error 22
```

Expected results:
"ci/prow/verify"should be passing

Additional info:

Comment 5 errata-xmlrpc 2022-02-16 11:19:40 UTC
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 (Moderate: OpenShift Container Platform 4.7.43 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0492