Description of problem: The object `prometheusrules.monitoring.coreos.com/kube-apiserver` in the openshift-kube-apiserver namespace still exists after an upgrade from 4.3.1 -> 4.3.8. This object should have been deleted, per Bug #1795617. If the PrometheusRule is manually deleted, it does not return. Version-Release number of selected component (if applicable): 4.3.8 How reproducible: This was seen on a cluster that was created on 4.1.34, upgraded to 4.2.18, then to 4.3.1, and lastly a force upgrade to 4.3.8 as an edge is not available. Steps to Reproduce: 1. Create cluster as above 2. Observe that the object still exists `oc get prometheusrules.monitoring.coreos.com/kube-apiserver -n openshift-kube-apiserver` 3. Remove object, and it will not return. Actual results: Alert still exists and will fire. Expected results: Alert is removed during the upgrade process and doesn't exist. Additional info:
I've opened https://github.com/openshift/openshift-docs/pull/20878 which will document the ability to remove that alert manually if one wishes to.
Maciej, Which specific 4.3.z did this alert go in? Why can't we put something in place to clean it up now that we've chosen to remove it?
PRs in the queue.
This waiting to be merged in the queue.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Adding UpcomingSprint since the bug is already in the queue and waiting for docs review.
This is already in the queue, waiting for merge.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I'm also waiting for OA decision since this backport is not a simple one.
It looks like this issue is not going to be merged. This problem was solved in newer versions of the product.