Description of problem: ImagePrunerDegraded repeatedly after deleting the jobs and getting an error "imagestream openshift/jboss-XXXXX-openshift: the server is currently unable to handle the request (get imagestreams.image.openshift.io jboss-XXXXXX-openshift)" Suggested to delete the jobs [ 8/25/2021 ] Again, the same issue repeated (the server is currently unable to handle the request) @ [ 9/6/2021 Version-Release number of selected component (if applicable): 4.7 How reproducible: [root@XXXXX-bastion tmp]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.16 True False 21d Error while reconciling 4.7.16: the update could not be applied Provider: AZURE Installation type: IPI Network environment: Connected Steps to Reproduce: 1. 2. 3. Actual results: [root@XXXXX-bastion XXXXXXXXXX]# oc logs pod/image-pruner-XXXXXXXX-XXXX 00:00:09.333809 1 prune.go:348] Creating image pruner with keepYoungerThan=1h0m0s, keepTagRevisions=3, pruneOverSizeLimit=<nil>, allImages=true Summary: deleted 0 objects imagestream openshift/jboss-XXXXX-openshift: the server is currently unable to handle the request (get imagestreams.image.openshift.io jboss-XXXX-openshift) imagestream openshift/rhdm-decisioncentral-rhel8: the server is currently unable to handle the request (get imagestreams.image.openshift.io rhdm-decisioncentral-rhel8) imagestream openshift/jboss-XXXX-62: the server is currently unable to handle the request (get imagestreams.image.openshift.io jboss-XXX-62) imagestream openshift/jboss-XXXXXX-openshift: the server is currently unable to handle the request (get imagestreams.image.openshift.io jboss-XXXX-openshift) Expected results: Additional info: Cu asked, How to disable the ImagePrunerJob for temporary and disable all Alerts.
Hello Team, Kindly update. Regards, Dr Vivek Yoganand
*** This bug has been marked as a duplicate of bug 1990125 ***