Bug 2107261
Summary: | [WMCO] WMCO endpoints missing after WMCO restart in vSphere | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jose Luis Franco <jfrancoa> |
Component: | Windows Containers | Assignee: | Sebastian Soto <ssoto> |
Status: | CLOSED ERRATA | QA Contact: | Ronnie Rasouli <rrasouli> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.11 | CC: | jvaldes, mburke, ssoto, stevsmit |
Target Milestone: | --- | ||
Target Release: | 4.12.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
* Previously, restarting the Windows Machine Config Operator (WMCO) in a cluster with running Windows nodes caused the Windows exporter endpoint to be removed. Because of this, each Windows node could not report any metrics data. With this update, the endpoint is retained when the WMCO is started. As a result, metrics data is reported properly after restarting WMCO. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2107261[*BZ#2107261*])
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-30 05:48:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2108805 |
Description
Jose Luis Franco
2022-07-14 15:30:41 UTC
WMCO VERSION ============== [jfrancoa@localhost wmco]$ oc get cm -n openshift-windows-machine-config-operator NAME DATA AGE kube-root-ca.crt 1 21m openshift-service-ca.crt 1 21m windows-machine-config-operator-lock 0 20m windows-services-6.0.0-07ebdd7 2 20m [jfrancoa@localhost wmco]$ oc get csv -n openshift-windows-machine-config-operator NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.v5.5.0 OpenShift Elasticsearch Operator 5.5.0 Succeeded windows-machine-config-operator.v6.0.0 Windows Machine Config Operator 6.0.0 Succeeded VALIDATION ============ [jfrancoa@localhost wmco]$ oc get endpoints -n openshift-windows-machine-config-operator NAME ENDPOINTS AGE windows-exporter 172.31.249.42:9182,172.31.249.201:9182 21m [jfrancoa@localhost wmco]$ oc get pods -n openshift-windows-machine-config-operator NAME READY STATUS RESTARTS AGE windows-machine-config-operator-554d8d85f4-4pqtj 1/1 Running 0 21m [jfrancoa@localhost wmco]$ oc delete pods windows-machine-config-operator-554d8d85f4-4pqtj -n openshift-windows-machine-config-operator pod "windows-machine-config-operator-554d8d85f4-4pqtj" deleted [jfrancoa@localhost wmco]$ oc get endpoints -n openshift-windows-machine-config-operator NAME ENDPOINTS AGE windows-exporter 172.31.249.42:9182,172.31.249.201:9182 4s 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: Red Hat OpenShift support for Windows Containers 7.0.0 [security 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. https://access.redhat.com/errata/RHSA-2022:9096 |