Bug 1825774

Summary: Keep reporting `secret \"pull-secret\" not found` in the samples operator log
Product: OpenShift Container Platform Reporter: XiuJuan Wang <xiuwang>
Component: SamplesAssignee: Gabe Montero <gmontero>
Status: CLOSED ERRATA QA Contact: XiuJuan Wang <xiuwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:28:40 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:

Description XiuJuan Wang 2020-04-20 09:06:15 UTC 
Description of problem:
samples-registry-crendentials secret has been removed as expected, but samples operator still reports "metrics pull secret retrieval failed with: secret \"pull-secret\" not found" .

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-04-18-184707

How reproducible:
always

Steps to Reproduce:
1.Check samples operator logs
2.
3.

Actual results:
Keep reporting "metrics pull secret retrieval failed with: secret \"pull-secret\" not found"

Expected results:
Should not report this error

Additional info:
Comment 3 Gabe Montero 2020-04-22 13:06:34 UTC 
this bug was introduced by the 4.5 change https://github.com/openshift/cluster-samples-operator/pull/249 where samples operator now takes advantage of internal image registry and associated imagestream related features introduced in 4.5 to use the install pull secret if it has credentials for the source image registry in question,
and with QE's quick discover was corrected before 4.5 shipped 

NO DOC UPDATE NEEDED
Comment 4 XiuJuan Wang 2020-04-24 03:29:38 UTC 
Can't reproduce this bug in 4.5.0-0.nightly-2020-04-24-001451 cluster.
Comment 5 errata-xmlrpc 2020-07-13 17:28: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, 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-2020:2409