Cause: intermittent API server errors were reported on the wrong condition (ImageChangesInProgress instead of SamplesExists) of the cluster operator config object.
Consequence: when API server communication returned and all the samples were installed, the samples operator would fail to switch Progressing to false because there was unexpected data in its ImageChangesInProgress condition, and upgrades would incorrectly be marked as incomplete.
Fix: code change was made to update SamplesExists with error reports on APIServer communication
Result: upgrades are no longer blocked if intermittent APIServer errors occur while samples operator is upgrading.
Delete apiserver pods during samples operator removing or creating imagestream, the APISERVER error reports in samplesexist part.
- lastTransitionTime: "2020-08-24T08:29:19Z"
lastUpdateTime: "2020-08-24T08:29:19Z"
message: 'imagestream create error: the server is currently unable to handle the request (post imagestreams.image.openshift.io)'
reason: APIServerServiceUnavailableError
status: Unknown
type: SamplesExist
Verified in 4.5.0-0.nightly-2020-08-20-031121 version
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 (OpenShift Container Platform 4.5.8 bug fix 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-2020:3510
Delete apiserver pods during samples operator removing or creating imagestream, the APISERVER error reports in samplesexist part. - lastTransitionTime: "2020-08-24T08:29:19Z" lastUpdateTime: "2020-08-24T08:29:19Z" message: 'imagestream create error: the server is currently unable to handle the request (post imagestreams.image.openshift.io)' reason: APIServerServiceUnavailableError status: Unknown type: SamplesExist Verified in 4.5.0-0.nightly-2020-08-20-031121 version