Bug 2108805 - [WMCO] WMCO endpoints missing after WMCO restart in vSphere
Summary: [WMCO] WMCO endpoints missing after WMCO restart in vSphere
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Windows Containers
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.11.0
Assignee: Sebastian Soto
QA Contact: Jose Luis Franco
URL:
Whiteboard:
Depends On: 2107261
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-19 21:00 UTC by OpenShift BugZilla Robot
Modified: 2022-08-23 06:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-23 06:32:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift windows-machine-config-operator pull 1144 0 None open [release-4.11] Bug 2108805: Maintain endpoint subsets on restart 2022-07-19 21:01:02 UTC
Red Hat Product Errata RHBA-2022:6129 0 None None None 2022-08-23 06:32:48 UTC

Comment 3 Jose Luis Franco 2022-07-26 09:16:42 UTC 
VERIFICATION
========================================
[jfrancoa@localhost openshift-tests-private]$ oc get endpoints -n openshift-windows-machine-config-operator
NAME               ENDPOINTS                              AGE
windows-exporter   172.31.249.59:9182,172.31.249.3:9182   163m
[jfrancoa@localhost openshift-tests-private]$ oc get pods -n openshift-windows-machine-config-operator 
NAME                                               READY   STATUS    RESTARTS   AGE
windows-machine-config-operator-6bc87c44f5-nwfsz   1/1     Running   0          164m
[jfrancoa@localhost openshift-tests-private]$ oc delete pod windows-machine-config-operator-6bc87c44f5-nwfsz -n openshift-windows-machine-config-operator 
pod "windows-machine-config-operator-6bc87c44f5-nwfsz" deleted
[jfrancoa@localhost openshift-tests-private]$ oc get endpoints -n openshift-windows-machine-config-operator
NAME               ENDPOINTS                              AGE
windows-exporter   172.31.249.59:9182,172.31.249.3:9182   1s

VERSION
=============================
[jfrancoa@localhost openshift-tests-private]$ oc get cm -n openshift-windows-machine-config-operator 
NAME                                   DATA   AGE
kube-root-ca.crt                       1      165m
openshift-service-ca.crt               1      165m
windows-machine-config-operator-lock   0      25s
windows-services-6.0.0-c79ccb0         2      164m

WINC-INDEX IMAGE HEAD: https://github.com/openshift/windows-machine-config-operator/commit/c79ccb0104c08b6981e12cd3f2447b006e5f4a06

[jfrancoa@localhost openshift-tests-private]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-07-24-151159   True        False         176m    Cluster version is 4.11.0-0.nightly-2022-07-24-151159

Test case RUN
==================
passed: (14m50s) 2022-07-26T09:15:56 "[sig-windows] Windows_Containers NonUnifyCI Longduration-Smokerun-Author:rrasouli-NonPreRelease-Critical-39858-Windows servicemonitor and endpoints check [Slow][Serial][Disruptive]"

1 pass, 0 skip (14m50s)
Comment 5 errata-xmlrpc 2022-08-23 06:32:44 UTC 
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 (Red Hat OpenShift support for Windows Containers 6.0.0 product release), 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-2022:6129
Note You need to log in before you can comment on or make changes to this bug.