Bug 1923802 - ci/prow/e2e-aws-olm build failing for openshift/cluster-resource-override-admission-operator
Summary: ci/prow/e2e-aws-olm build failing for openshift/cluster-resource-override-adm...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Elana Hashman
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1923774
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-01 23:33 UTC by Elana Hashman
Modified: 2021-02-24 15:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1923774
Environment:
Last Closed: 2021-02-24 15:57:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-resource-override-admission-operator pull 53 0 None closed Bug 1923802: Update yq commands 2021-02-11 23:29:13 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:58:06 UTC

Description Elana Hashman 2021-02-01 23:33:54 UTC
+++ This bug was initially created as a clone of Bug #1923774 +++

Description of problem:

```
the build root failed after 39s with reason DockerBuildFailed: Dockerfile build strategy has failed.

usage: go get [-d] [-t] [-u] [-v] [-insecure] [build flags] [packages]
Run 'go help get' for details.
subprocess exited with status 2
subprocess exited with status 2
error: build error: error building at STEP "RUN GO111MODUL...et -mod=readonly github.com/mikefarah/yq/v2": exit status 2
```

See e.g. https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/15420/rehearse-15420-pull-ci-openshift-cluster-resource-override-admission-operator-master-unit/1356337961301446656


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


How reproducible:

Failing since Jan. 28, likely due to the golang 1.15 bump: https://github.com/openshift/cluster-resource-override-admission-operator/pull/51


Additional info:

--- Additional comment from Elana Hashman on 2021-02-01 23:08:04 UTC ---

Build is now fixed. I need to submit one follow-up PR to fix the yq issue.

--- Additional comment from OpenShift Automated Release Tooling on 2021-02-01 23:23:17 UTC ---

Elliott changed bug status from MODIFIED to ON_QA.



--- 

yq issue:

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-resource-override-admission-operator/53/pull-ci-openshift-cluster-resource-override-admission-operator-master-e2e-aws-olm/1356353821017640960

+ sed 's,CLUSTERRESOURCEOVERRIDE_OPERAND_IMAGE,"registry.build01.ci.openshift.org/ci-op-vtvg1wsd/stable:cluster-resource-override-admission",g' -i ./_output/olm/registry/registry-deployment.yaml
./hack/deploy-operator-registry.sh clusterresourceoverride-operator /cli/oc ""./_output"/olm/registry"
setting up namespace
namespace/clusterresourceoverride-operator created
applying configmap
configmap/clusterresourceoverride-operator-registry-env created
creating deployment
Error: unknown command "r" for "yq"
Run 'yq --help' for usage.
could not retrieve Deployment name from ./_output/olm/registry/registry-deployment.yaml
make: *** [operator-registry-deploy] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2021-02-01T22:05:49Z"}
error: failed to execute wrapped command: exit status 2

Comment 2 Sunil Choudhary 2021-02-03 05:37:53 UTC
I see this is for update in yq commands, marking it verified.

Comment 5 errata-xmlrpc 2021-02-24 15:57:46 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.0 security, bug fix, and enhancement 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-2020:5633


Note You need to log in before you can comment on or make changes to this bug.