*** Bug 1842561 has been marked as a duplicate of this bug. ***
The latest payload 4.4.0-0.nightly-2020-06-03-225439 don't included the fix, waiting for new payload.
I got the APIServerServiceUnavailableError in openshift-samples clusteroperator after delete three nopenshift-apiserver pods against 4.4.0-0.nightly-2020-06-07-075345 A. 1) mark samples operator removed 2) scale down / kill the 3 openshift api server pods 3) then catch the openshift-samples clusteroperator being in degraded status and see what the reason is conditions: - lastTransitionTime: "2020-06-08T08:29:54Z" status: "False" type: Available - lastTransitionTime: "2020-06-08T08:29:54Z" message: 'Samples installation in error at 4.4.0-0.nightly-2020-06-07-075345: APIServerServiceUnavailableError' status: "True" type: Progressing - lastTransitionTime: "2020-06-08T08:29:54Z" message: The error the server is currently unable to handle the request (get imagestreams.image.openshift.io) during openshift namespace cleanup has left the samples in an unknown state; reason: APIServerServiceUnavailableError status: "True" type: Degraded extension: null B. 1) mark samples operator removed 2)Wait samples are removed, mark samples to Managed 3) kill the 3 openshift api server pods 4) then catch the openshift-samples clusteroperator being in degraded status and see what the reason is status: conditions: - lastTransitionTime: "2020-06-08T08:28:28Z" status: "False" type: Available - lastTransitionTime: "2020-06-08T08:28:28Z" message: 'Samples installation in error at 4.4.0-0.nightly-2020-06-07-075345: APIServerServiceUnavailableError' status: "True" type: Progressing - lastTransitionTime: "2020-06-08T08:28:31Z" message: 'error creating samples: the server is currently unable to handle the request (post imagestreams.image.openshift.io);imagestream create error: the server is currently unable to handle the request (post imagestreams.image.openshift.io);' reason: APIServerServiceUnavailableError status: "True" type: Degraded
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:2445