Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1910150

Summary:	Brew build failing: unreadable_file.yaml is outside of cloned repository
Product:	OpenShift Container Platform	Reporter:	W. Trevor King <wking>
Component:	OpenShift Update Service	Assignee:	Lalatendu Mohanty <lmohanty>
OpenShift Update Service sub component:	operand	QA Contact:	liujia <jiajliu>
Status:	CLOSED ERRATA	Docs Contact:	Kathryn Alexander <kalexand>
Severity:	high
Priority:	high	CC:	lmohanty
Version:	4.6
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-15 16:20:30 UTC	Type:	Bug
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:
Bug Blocks:	1910154

Description W. Trevor King 2020-12-22 20:43:03 UTC

From Brew:

  Image build failed. Error in plugin resolve_remote_source: Cachito request is in "failed" state, reason: The destination of 'cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/test_fixtures/invalid0/cincinnati-graph-data/blocked-edges/unreadable_file.yaml' is outside of cloned repository

That file is a link to /does/not/exist [1], and we should drop it to keep Brew happy.  We could also point it somewhere inside the repo (./does/not/exist?), but that can happen in some future feature work if we want to ensure the broken-symlink content doesn't break the plugin.  I'm not all that worried about hitting broken symlinks in the wild ;).

[1]: https://github.com/openshift/cincinnati/pull/307/files#diff-4ff999d99eb12d271b0ab83ee6017fea096e409defd79df6b2422d9e920aa962R1

Comment 2 liujia 2020-12-23 02:49:09 UTC

Since the original issue break brew build down. So qe will verify the issue once latest osus image build is available. Just from ci test result(https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cincinnati/350/pull-ci-openshift-cincinnati-master-e2e/1341432697683185664), the pr might not involve regression issue now.

Comment 3 liujia 2021-01-25 02:34:23 UTC

I notice there is a cloned bug for 4.6(#1910154), so will check osus image build issue in the bug of v4.6 which is for v4.6 osus image. And according to comment2, verify this bug.

Comment 4 W. Trevor King 2021-07-20 15:21:01 UTC

We won't cut 4.7 or 4.8 operators; moving to 4.9.0 (folks with 4.6 releases will be able to update straight to 4.9).

Comment 7 errata-xmlrpc 2021-10-15 16:20:30 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 (RHEA: OSUS 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/RHBA-2021:3735