Description of problem:
mapi_instance_create_failed doesn't work on vsphere
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a failed machine by setting template to an invalid one
2.Check prometheus metrics
Prometheus web console show "No datapoints found".
$ token=`oc sa get-token prometheus-k8s -n openshift-monitoring`
$ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep "mapi_instance_"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 64475 0 64475 0 0 530k 0 --:--:-- --:--:-- --:--:-- 533k
$ oc get machine
NAME PHASE TYPE REGION ZONE AGE
zhsunvs22-tr2bv-master-0 Running 15h
zhsunvs22-tr2bv-master-1 Running 15h
zhsunvs22-tr2bv-master-2 Running 15h
zhsunvs22-tr2bv-worker-5d6xw Running 15h
zhsunvs22-tr2bv-worker-xrw84 Running 15h
zhsunvs22-tr2bv-worker1-sjkss Failed 13h
Should show mapi_instance_create_failed detail info.
The PR is going to be merged today/tomorrow, QA already confirmed the bug is not present. Still, will tag this BZ with upcoming sprint for a case of unexpected delays.
Validated on -
1.Copy machineset to create an invalid image machineset
2.machine created in failed state when scaled
mapi_instance_create_failed metric recorded successfully
Moved to verified
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.