Description of problem: The ALERTS{alertname="KubeVersionMismatch",alertstate="firing",severity="warning"} was blocking merging the Openshift API server bump to kubernetes 1.16.0. This was because the kubernetes apiserver was still running on 1.14.0 for that PR. Having an alert for this kind of mismatch does not make sense as it is normal that components can run on version skew (typically during upgrade, see: https://bugzilla.redhat.com/show_bug.cgi?id=1684431) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Not a 4.2 blocker, but something we should fix in upstream during 4.3
(In reply to Michal Fojtik from comment #1) > Not a 4.2 blocker, but something we should fix in upstream during 4.3 How long does an upgrade take? We are thinking of increasing the time for this.
Tested with 4.4.0-0.nightly-2020-01-15-181917, KubeVersionMismatch alert is removed # token=`oc -n openshift-monitoring sa get-token prometheus-k8s` # oc -n openshift-monitoring exec -c prometheus prometheus-k8s-1 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/rules' | jq | grep "KubeVersionMismatch" nothing returned
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:0581
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days