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

Bug 1910154

Summary:	Brew build failing: unreadable_file.yaml is outside of cloned repository
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	OpenShift Update Service	Assignee:	W. Trevor King <wking>
OpenShift Update Service sub component:	operand	QA Contact:	liujia <jiajliu>
Status:	CLOSED CURRENTRELEASE	Docs Contact:	Kathryn Alexander <kalexand>
Severity:	high
Priority:	high	CC:	bleanhar, jiajliu, lmohanty, vlaad, wking
Version:	4.6
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-14 15:43:25 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:	1910150
Bug Blocks:

Description OpenShift BugZilla Robot 2020-12-22 21:06:19 UTC

+++ This bug was initially created as a clone of Bug #1910150 +++

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 3 liujia 2021-01-26 07:59:39 UTC

Set the status back since Elliott add it to wrong advisory.

Comment 5 liujia 2021-02-08 03:25:02 UTC

Hi Trevor

Since the new build was available now(https://errata.devel.redhat.com/advisory/67040), i think we can get this bug's status updated to ON_QA due to related https://github.com/openshift/cincinnati/pull/351 was merged yet. It's out of ocp release scope, so i'm not sure if any bot or release manager will do it for us. hdyt?

Comment 6 W. Trevor King 2021-02-08 03:39:09 UTC

I'm a bit fuzzy on the release process, but yeah, I think Lala built a candidate bundle since that PR landed.

Comment 7 liujia 2021-02-08 07:52:15 UTC

According https://bugzilla.redhat.com/show_bug.cgi?id=1910150#c2, now we can build osus images with the pipeline successfully, so move the bug to verify.

Comment 11 Lalatendu Mohanty 2021-06-14 15:43:08 UTC

Closing this bug as this is got fixed  in 4.6 branch as well through https://bugzilla.redhat.com/show_bug.cgi?id=1910150