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

Bug 1782204

Summary: static pod operator revision pending message is unclear
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: kube-apiserverAssignee: David Eads <deads>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, gblomqui, mfojtik, xxia
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1781804 Environment:
Last Closed: 2020-01-23 11:18:55 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: 1781804    
Bug Blocks:    

Description David Eads 2019-12-11 12:33:19 UTC
+++ This bug was initially created as a clone of Bug #1781804 +++

This makes debugging harder than it needs to be and I'm currently looking at an issue where we appear stuck here.

Comment 2 Xingxing Xia 2019-12-17 11:15:55 UTC
Per https://github.com/openshift/library-go/pull/641/files#diff-aea28fda19fe8a3c27c2cf6590e72d89R538 , tried to make the env to have an succeeded installer pod while latestRevisionAvailable > currNodeState.TargetRevision but no idea how to make it. Turned to search https://search.svc.ci.openshift.org/?search=has+been+installed%2C+but+is+not+ready&maxAge=48h&context=2&type=all found occurrences like "static pod of revision 2 has been installed, but is not ready while new revision 4 is pending" that has displayed "static pod of revision %d". Lowering it is not a serious function issue, only a debugging enhancement.

Comment 4 errata-xmlrpc 2020-01-23 11:18:55 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:0062