Bug 1782204 - static pod operator revision pending message is unclear
Summary: static pod operator revision pending message is unclear
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.3.0
Assignee: David Eads
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1781804
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-11 12:33 UTC by David Eads
Modified: 2020-01-23 11:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1781804
Environment:
Last Closed: 2020-01-23 11:18:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift library-go pull 641 0 None closed bug 1782204: [release-4.3] bug 1781804: fix revision pending message 2020-08-04 08:33:28 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:15 UTC

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


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